Scaffold AGENT.md, AGENTGOAL.md, AGENTHARNESS.md, and AGENTPROGRESS.md into a target directory with strict, non-overlapping functional boundaries for governance, long-term mission, reusable playbook, and live state. Use when a workspace needs a disciplined, recoverable agent-file contract.
Turn the current chat history and optional pasted agent transcripts into a reusable skill package. Use when a conversation already contains a repeatable workflow that should be drafted in the current project .temp/ folder and optionally published into a skill-marketplace-template-style marketplace. Do not use it for…
Use when starting, planning, steering, or reviewing an agent-assisted task where requirements, codebase constraints, domain knowledge, taste, or acceptance criteria are unclear and hidden assumptions could cause rework.
Scaffold a two-level parent + children agent-file hierarchy in one shot. Delegates per-node base scaffolding to the agent-files skill, then installs immutable child-specific control files or verifies compatible existing ones so every node is internally consistent on first read. Use when a workspace needs a nested…
Plan, review, or revise IEEE Communications Society Related Work sections by deriving comparisons from the manuscript, checking claims against primary sources, using a literature ledger when available, and locating a concrete communications or networking gap. Do not use for bibliography-only cleanup or broad surveys…
Extend manuscript-writing-agent-files for LaTeX IEEE-style manuscript revision by installing a bounded revision-response harness patch and adding REVISIONTASK.md for joint manuscript and response-letter drafting. Use when a manuscript-writing workspace needs revision-response coordination without weakening the parent…
Extend agent-files for standalone LaTeX IEEE-style manuscript writing by invoking the base four-file scaffold with immutable AGENT.md and installing a bounded manuscript-writing harness patch. Use when a paper workspace needs a disciplined, recoverable manuscript-writing agent-file contract.
Curate an existing AGENTGOAL.md from a research brief and optional chat context. Use when a workspace already has AGENTGOAL.md and the user wants to refine or save an explicit research goal. Do not use it to scaffold AGENT files, rewrite AGENT.md or other agent files, or infer a final goal without interacting with the…
Create a low-entropy review/ workspace from a user's research intention. Use when a project needs a literature-review folder with nested agent files, root review docs, a reusable note template, and topic-derived theme folders. Do not use it to seed a paper corpus or to curate an existing review in place without first…
Build and query the parent/child dependency graph across all skills in a marketplace. Use when auditing for overlapping functionality, finding consumers of a skill, or answering "what depends on X?" without storing a separate children list. Do not use this skill to edit skill metadata or create new skills.
Scaffold AGENTVOCABULARY.md next to an agent-files contract as the single wording authority for a workspace, with noun/adjective/verb lists kept plain, self-contained, and synonym-free, plus the workflow to load words from the workspace's documents and code and merge them. Use when a workspace's reports and code need…