agentleFS
Sign inStart free
int2t05int2t05/engineering-skills/skills/meta/using-skills/SKILL.md

using-skills

Skill3 starsChanged 29 days agoMITView on GitHub

Choose the smallest applicable workflow when task routing is uncertain. Triggers on "which skill should I use", "用哪个技能".

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing-skills.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    writing-skills

    Use when creating new skills, editing existing skills, or verifying skills work before deployment

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Using Skills

When to use

  • Choose the smallest applicable workflow when task routing is uncertain.

Not for: clear tasks with a selected skill; skill-authoring for maintenance.

Steps

  1. Identify intent, scope and uncertainty; use a clear skill directly and avoid ritual routing for simple questions.
  2. Choose by output and problem; clarify only if alternative interpretations change the work.
  3. Sequence only necessary prerequisites and reuse confirmed artifacts instead of forcing every lifecycle stage.
  4. Load the skill and only needed references; use ordinary engineering judgment if none fits and identify recurring gaps.

Verify

  • Selected workflow fits intent; unnecessary skills, artifacts and repeated approval requests are avoided.

Phase catalog

  • 01-product — brainstorm, oss-strategy, spec
  • 02-research — research
  • 03-design — api-design, architecture, codebase-design, design-research, domain-modeling, frontend-design, image-to-code, imagegen, prompt-engineering, prototype, schema-design
  • 04-develop — auth-implementation, breakdown, context-engineering, error-handling, i18n, implement, multi-agent-orchestration
  • 05-tune — cost-optimization, performance, refactoring, simplify
  • 06-test — api-testing, e2e-testing, load-testing, tdd, test-generation
  • 07-verify — a11y-review, code-review, debugging, linting, security-review
  • 08-ship — ci-cd, deprecation-migration, git-workflow, oss-polish, shipping
  • 09-operate — documentation-audit, handoff, incident-response, observability, purity-audit
  • meta — skill-authoring, using-skills

References

  • engineering-principles.md — shared decision boundaries, scope and verification.
  • references/phase-tree.md — full ASCII decision tree by phase and task shape.

External skill discovery (npx skills find/add) is out of scope — this router maps tasks to this collection's internal skills only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free