skills/skillkit-help/template/SKILL.md
One sentence: what this skill does and when to invoke it. Use for: [list 2-3 trigger phrases users would naturally type].
npx skillsauth add rfxlamia/skillkit your-skill-nameInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
[2-3 sentences: what this skill does and why it exists. Be specific. Bad: "Helps with code." Good: "Reviews Python functions for PEP-8 compliance and common anti-patterns, then outputs a prioritized fix list."]
[Optional but recommended for complex skills. List the specific conditions that should trigger this skill.]
Examples:
[Instructions for the agent. Be explicit — don't say "do the right thing," say exactly what to do. Use numbered steps for ordered workflows, bullet points for flexible guidance.]
[Continue as needed. Each section should have one clear responsibility.]
[Put bulky reference material here rather than in the main flow. The agent loads this only when needed, saving tokens.]
tools
Toolkit for creating and validating skills and subagents. Use when: creating a new skill (fast or full mode), validating an existing skill, deciding Skills vs Subagents, migrating docs to skills, estimating token cost, or running a security scan. Triggers: "create skill", "build skill", "validate skill", "new subagent", "skills vs subagents", "estimate tokens", "security scan".
development
Pre-build orientation for skill creators. Answers "what are skills?", "should I make one?", and "is my skill good enough?" before you start building. Use for: understand skills, decide skills vs subagents, validate an existing skill. When ready to actually build, invoke /skillkit directly instead.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------