kickoff-doc
Turn a shaped project kickoff transcript into a reference document for the builder. Use when the user has a transcript (VTT, etc.) from a kickoff call and wants to produce a document that captures what was shaped and agreed.
86
83%
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-structured skill description with clear 'what' and 'when' components and good trigger terms including file format mentions. The main weakness is the lack of specific concrete actions - it describes the transformation at a high level but doesn't enumerate what the reference document will contain or what processing steps are involved.
Suggestions
Add specific concrete actions like 'extracts decisions, action items, scope boundaries, and stakeholder agreements' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (project kickoff transcript) and the output (reference document), but lacks specific concrete actions like 'extract action items', 'identify stakeholders', or 'summarize decisions'. The phrase 'captures what was shaped and agreed' is somewhat vague. | 2 / 3 |
Completeness | Clearly answers both what ('Turn a shaped project kickoff transcript into a reference document') and when ('Use when the user has a transcript from a kickoff call and wants to produce a document'). Has explicit 'Use when...' clause with clear trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'transcript', 'VTT', 'kickoff call', 'shaped project', 'reference document'. The parenthetical '(VTT, etc.)' adds a useful file format trigger. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining 'shaped project', 'kickoff transcript', and 'reference document for the builder'. Unlikely to conflict with generic transcript or document skills due to the specific workflow context. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill that provides clear guidance for transforming kickoff transcripts into builder-facing documents. Its main strengths are the concrete structure template, explicit process steps, and the 'territory not timeline' organizing principle. Minor improvements could come from tightening some explanatory sections and considering whether the voice/style guidelines warrant a separate reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant explanations (e.g., the 'Voice: Use Their Words' section repeats the 'point to a moment' test concept). Some sections could be tightened without losing clarity. | 2 / 3 |
Actionability | Provides concrete, specific guidance throughout: clear structure template, explicit do/don't lists, a specific 7-step process, and a concrete test ('can you point to where each claim was said?'). The guidance is immediately usable. | 3 / 3 |
Workflow Clarity | The 7-step process is clearly sequenced with logical ordering (read full transcript first, identify areas, draft frame, etc.). Step 7 provides explicit validation ('Review against the transcript'). For a document-creation skill, this is appropriately thorough. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but everything is inline in one file. For a skill of this length (~100 lines), some content like the detailed 'Voice' guidelines or the 'Design Decisions' philosophy could potentially be referenced separately, though the current structure is functional. | 2 / 3 |
Total | 10 / 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
- rjs/shaping-skills
- Commit
7d8c311
- 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.