startup-context
When the user wants to create or update their startup context document. Also use when the user mentions "set up context", "tell you about my startup", or any other skill needs context that doesn't exist yet.
81
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/startup-context/SKILL.mdQuality
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 description is strong on trigger terms, completeness, and distinctiveness, clearly communicating when Claude should select this skill. Its main weakness is that the 'what' portion could be more specific about the concrete actions involved (e.g., what information is gathered, what the document structure looks like). Overall it's a solid functional description that would work well in a multi-skill selection scenario.
Suggestions
Add more specific concrete actions to the 'what' portion, e.g., 'Creates or updates a startup context document capturing company name, stage, product description, target market, and key metrics.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'create or update their startup context document' which names a domain and a couple of actions, but doesn't list specific concrete actions like what the document contains, what fields are captured, or what format is produced. | 2 / 3 |
Completeness | Clearly answers both 'what' (create or update startup context document) and 'when' (explicit triggers including quoted phrases and the fallback condition of another skill needing context that doesn't exist). The 'Use when' equivalent is explicitly stated. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'set up context', 'tell you about my startup', and the broader trigger of needing context that doesn't exist yet. These are realistic phrases a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The skill has a clear niche around startup context documents specifically, with distinct triggers like 'tell you about my startup' and 'set up context'. This is unlikely to conflict with other skills since it targets a very specific document type and use case. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid, actionable framework for gathering startup context with a well-structured template and thoughtful interview flow. Its main weaknesses are the inline verbosity of the full template (which could be a referenced file) and the lack of explicit validation/confirmation steps in the workflow. The interview questions are well-grouped but partially redundant with the template fields.
Suggestions
Add an explicit validation step after generating the context file — e.g., 'Show the user a summary of key fields and confirm accuracy before writing'
Move the full context document template to a separate file (e.g., templates/startup-context-template.md) and reference it from the skill to reduce inline length
Remove the opening explanatory sentence ('This is the foundation skill...') — this describes purpose rather than providing actionable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The context document template is useful but quite lengthy. The interview questions section partially duplicates what the template already implies. Some instructions like 'This is the foundation skill' and 'Every other skill reads this context first' are explanatory rather than actionable. | 2 / 3 |
Actionability | Provides a concrete, copy-paste-ready markdown template for the context file, specific file path (.agents/startup-context.md), structured interview questions grouped into rounds, and clear instructions on what to write and where. | 3 / 3 |
Workflow Clarity | The 4-step workflow is clear and sequenced, but lacks validation checkpoints — there's no step to confirm the generated context with the user before finalizing, no verification that all critical fields are populated, and no explicit feedback loop for corrections beyond the general 'keep it updated' note. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the full context document template is inlined (60+ lines) when it could be referenced as a separate template file. For a skill of this length (~90 lines of content), splitting the template out would improve scannability. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- shawnpang/startup-founder-skills
- Commit
4ad31b4
- 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.