common-workflow-writing
Rules for writing concise, token-efficient workflow and skill files. Prevents over-building that requires costly optimization passes. Use when creating or editing workflow files, SKILL.md files, or new skill definitions. (triggers: .agent/workflows/*.md, SKILL.md, create workflow, write workflow, new skill, new workflow)
96
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-constructed description that clearly communicates its niche purpose and includes explicit trigger guidance with both natural language terms and file path patterns. Its main weakness is that the 'what' portion could be more specific about the concrete actions or rules it enforces, rather than staying at the level of 'rules for writing concise files'. Overall it performs strongly across most dimensions.
Suggestions
Add 2-3 more specific concrete actions to improve specificity, e.g., 'Enforces brevity guidelines, validates structure, removes redundant sections, and caps token usage in workflow and skill files.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (workflow and skill files) and a general action (writing concise, token-efficient files, prevents over-building), but doesn't list multiple specific concrete actions like 'enforce line limits, remove redundant sections, validate token counts'. | 2 / 3 |
Completeness | Clearly answers both 'what' (rules for writing concise, token-efficient workflow and skill files; prevents over-building) and 'when' (explicit 'Use when' clause with specific triggers for creating/editing workflow files, SKILL.md files, or new skill definitions). | 3 / 3 |
Trigger Term Quality | Includes a good range of natural trigger terms that users would actually say: 'workflow files', 'SKILL.md', 'create workflow', 'write workflow', 'new skill', 'new workflow', plus file path patterns like '.agent/workflows/*.md'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | Targets a very specific niche — writing workflow and skill definition files with token-efficiency constraints. The explicit file path triggers (.agent/workflows/*.md, SKILL.md) make it clearly distinguishable from general coding or documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent meta-skill that embodies its own principles — it's concise, actionable, and well-structured. The size limits table, required workflow structure, and anti-patterns list provide concrete, immediately usable guidance. The self-check checklist is a smart validation mechanism that ensures quality before committing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely lean and practices what it preaches. Every line serves a purpose — no unnecessary explanations, no padding, no concepts Claude already knows. The anti-patterns section uses inline before/after format efficiently. | 3 / 3 |
Actionability | Provides concrete, specific rules with exact size limits, a required structure template, and a self-check checklist. The anti-patterns section gives specific examples of what to delete. The guidance is immediately actionable without ambiguity. | 3 / 3 |
Workflow Clarity | For a meta-skill about writing workflows, the process is clear: follow core rules → respect size limits → use required structure → avoid anti-patterns → run self-check. The self-check checklist serves as an explicit validation step before saving, which is appropriate for this type of skill. | 3 / 3 |
Progressive Disclosure | The skill is under 50 lines of actual content and well-organized into clearly labeled sections (Core Rules, Size Limits, Structure, Anti-Patterns, Self-Check). References to `references/` directories are mentioned as overflow targets, which is appropriate guidance without needing separate files for this concise skill. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.