cc-skill-project-guidelines-example
Project Guidelines Skill (Example)
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill cc-skill-project-guidelines-example69
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 94%
↑ 1.74xAgent success when using this skill
Validation for skill structure
Discovery
0%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 essentially a placeholder title rather than a functional skill description. It provides no information about capabilities, use cases, or trigger conditions. It would be impossible for Claude to determine when to select this skill from a list of alternatives.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Enforces coding standards, validates project structure, checks documentation requirements')
Include an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks about project standards, coding conventions, or documentation requirements')
Specify what type of project guidelines this covers to distinguish it from other potential guideline-related skills (e.g., 'Python project guidelines' vs 'API design guidelines')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description 'Project Guidelines Skill (Example)' contains no concrete actions whatsoever - it merely names itself with a parenthetical noting it's an example. No verbs or capabilities are described. | 1 / 3 |
Completeness | Fails to answer both 'what does this do' and 'when should Claude use it'. There is no description of functionality and no 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. 'Project Guidelines' is vague and 'Skill (Example)' is meta-language about the skill itself, not trigger terms for when to use it. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'Project Guidelines' could overlap with any skill related to projects, documentation, standards, or guidelines. No distinguishing characteristics provided. | 1 / 3 |
Total | 4 / 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 is a solid project guidelines template with excellent actionability through concrete, executable code examples. However, it's verbose for a SKILL.md overview—detailed code patterns and test structures would be better in referenced files. The deployment workflow lacks explicit validation checkpoints and error recovery guidance.
Suggestions
Move detailed code patterns (API response format, hooks, Claude integration) to a separate PATTERNS.md file and reference it from the main skill
Add explicit validation steps to the deployment workflow: 'If build fails: check X, fix Y, retry'
Remove the 'When to Use' section—Claude understands when to reference project-specific skills
Add a feedback loop to the deployment checklist: 'After deploy: verify health endpoint, check logs for errors, rollback if needed'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity. The 'When to Use' section explains what project skills contain (which Claude would understand), and some code examples include comments/patterns Claude already knows (like basic try/catch, generic API response patterns). | 2 / 3 |
Actionability | Provides fully executable code examples across Python, TypeScript, and bash. Code patterns are copy-paste ready with complete implementations for API responses, Claude integration, React hooks, and test structures. | 3 / 3 |
Workflow Clarity | The deployment workflow has a checklist and commands, but lacks explicit validation checkpoints and feedback loops. There's no 'if deployment fails, do X' guidance, and the testing section doesn't integrate into a clear pre-commit/pre-deploy workflow with verification steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic (~300 lines) with detailed code examples that could be split into separate reference files. The 'Related Skills' section at the end suggests external files but the main content doesn't leverage progressive disclosure effectively. | 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 | |
- 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.