skill-latex-research
- Repo stars 435
- Author repo nvim
LaTeX Research Skill
Thin wrapper that delegates LaTeX research to latex-research-agent subagent.
Trigger Conditions
This skill activates when:
- Task type is "latex"
- Research involves LaTeX documentation
- LaTeX-specific research is needed
Execution Flow
Stage 1: Input Validation
Validate task_number exists.
Stage 2: Preflight Status Update
Update status to "researching" BEFORE invoking subagent.
Stage 3: Prepare Delegation Context
Include task_context, focus_prompt, metadata_file_path.
Stage 4: Invoke Subagent
Use Agent tool with subagent_type: "latex-research-agent".
Stage 4b: Self-Execution Fallback
CRITICAL: If you performed the work above WITHOUT using the Agent tool (i.e., you read files,
wrote artifacts, or updated metadata directly instead of spawning a subagent), you MUST write a
.return-meta.json file now before proceeding to postflight. Use the schema from
return-metadata-file.md with the appropriate status value for this operation.
If you DID use the Agent tool, skip this stage -- the subagent already wrote the metadata.
Postflight (ALWAYS EXECUTE)
The following stages MUST execute after work is complete, whether the work was done by a subagent or inline (Stage 4b). Do NOT skip these stages for any reason.
Stage 5: Parse Subagent Return
Read the metadata file from specs/{N}_{SLUG}/.return-meta.json.
Stage 6: Update Task Status (Postflight)
Update state.json and TODO.md based on result.
Stage 7: Link Artifacts
Add research artifact to state.json. Update TODO.md per @.claude/context/patterns/artifact-linking-todo.md with field_name=**Research**, next_field=**Plan**.
Stage 8: Git Commit
Commit changes with session ID.
Stage 9: Return Brief Summary
Error Handling
Input Validation Errors
Return immediately if task not found.
Metadata File Missing
Keep status as "researching", report error.
Git Commit Failure
Non-blocking: Log failure but continue.
Return Format
Brief text summary (NOT JSON).
- Fluxly category
- Documentation
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Author / version / license
- @benbrastmckie · no license declared
- Fluxly token estimate
- Lean
- Fluxly setup estimate
- Guided setup
- External API key
- No requirement detected
- Detected OS requirements
- Unspecified
- Runtime requirements
- Unspecified
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Detected network behavior
- Local-only
- Install commands
- None (reference only)
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
The current SKILL.md does not define a fixed output example. This skill activates when: Task type is "latex" Research involves LaTeX documentation
Execution Flow
Validate tasknumber exists.
Update status to "researching" BEFORE invoking subagent.
Include taskcontext, focusprompt, metadatafilepath.
Use Agent tool with subagenttype: "latex-research-agent".
# LaTeX Research Skill
Thin wrapper that delegates LaTeX research to `latex-research-agent` subagent.
## Trigger Conditions
This skill activates when:
- Task type is "latex"
- Research involves LaTeX documentation
- LaTeX-specific research is needed
## Execution Flow
### Stage 1: Input Validation
Validate task_number exists.
### Stage 2: Preflight Status Update
Update status to "researching" BEFORE invoking subagent.
### Stage 3: Prepare Delegation Context
Include task_context, focus_prompt, metadata_file_path.
### Stage 4: Invoke Subagent
Use Agent tool with subagent_type: "latex-research-agent".
### Stage 4b: Self-Execution Fallback
**CRITICAL**: If you performed the work above WITHOUT using the Agent tool (i.e., you read files,
wrote artifacts, or updated metadata directly instead of spawning a subagent), you MUST write a
`.return-meta.json` file now before proceeding to postflight. Use the schema from
`return-metadata-file.md` with the appropriate status value for this operation.
If you DID use the Agent tool, skip this stage -- the subagent already wrote the metadata.
## Postflight (ALWAYS EXECUTE)
The following stages MUST execute after work is complete, whether the work was done by a
subagent or inline (Stage 4b). Do NOT skip these stages for any reason.
### Stage 5: Parse Subagent Return
Read the metadata file from `specs/{N}_{SLUG}/.return-meta.json`.
### Stage 6: Update Task Status (Postflight)
Update state.json and TODO.md based on result.
### Stage 7: Link Artifacts
Add research artifact to state.json. Update TODO.md per `@.claude/context/patterns/artifact-linking-todo.md` with `field_name=**Research**`, `next_field=**Plan**`.
### Stage 8: Git Commit
Commit changes with session ID.
### Stage 9: Return Brief Summary
## Error Handling
… Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.
sections -> Trigger Conditions → Execution Flow → Stage 1: Input Validation → Stage 2: Preflight Status Update → Stage 3: Prepare Delegation Context → Stage 4: Invoke Subagent
terms -> CRITICAL · Research · Plan · Thin wrapper that delegates LaTeX research to latex-research-agent subagent. · If you DID use the Agent tool, skip this stage -- the subagent already wrote the metadata. · The following stages MUST execute after work is complete, whether the work was done by a subagent or inline (Stage 4b). · Brief text summary (NOT JSON).
files/cmd -> latex-research-agent · .return-meta.json · return-metadata-file.md · specs/{N}{SLUG}/.return-meta.json · @.claude/context/patterns/artifact-linking-todo.md · fieldname=Research · nextfield=Plan
body sha256 -> 02ef6a378713
Decide Fit First
Design Intent
How To Use It
Boundaries And Review