cc-skill-project-guidelines-example
Project Guidelines Skill (Example)
50
Quality
32%
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 ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/cc-skill-project-guidelines-example/SKILL.mdQuality
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 zero information about capabilities, use cases, or trigger conditions. It would be impossible for Claude to make an informed decision about when to select this skill from a list of alternatives.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Reads and applies project-specific coding standards, naming conventions, and architectural patterns from GUIDELINES.md files')
Include an explicit 'Use when...' clause with trigger terms (e.g., 'Use when the user asks about project conventions, coding standards, style guidelines, or how things should be done in this codebase')
Add natural keywords users would say such as 'coding standards', 'conventions', 'style guide', 'best practices', 'how we do X here'
| 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 explanation of functionality and no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains only generic terms 'Project' and 'Guidelines' with no natural keywords users would say. No file types, specific actions, or domain-specific terminology that would help match user requests. | 1 / 3 |
Distinctiveness Conflict Risk | 'Project Guidelines' is extremely generic and could conflict with any skill related to projects, documentation, coding standards, or guidelines. No distinct triggers or niche defined. | 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 across the full stack. However, it's somewhat verbose for a SKILL.md overview and would benefit from splitting detailed code patterns into 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 overview
Add explicit validation steps to the deployment workflow: 'If build fails, check X. If deploy fails, run Y to diagnose'
Remove the 'When to Use' section - Claude understands when to reference project-specific skills without explanation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity like the 'When to Use' section explaining what project skills contain (Claude knows this). The architecture diagram and code examples are useful but could be tighter. | 2 / 3 |
Actionability | Provides fully executable code examples for API responses, frontend calls, Claude integration, custom hooks, and tests. Commands are copy-paste ready with specific paths and flags. | 3 / 3 |
Workflow Clarity | Deployment workflow has a checklist and commands, but lacks explicit validation checkpoints and feedback loops. No 'if deployment fails, do X' recovery steps. Testing section shows commands but doesn't integrate into a clear workflow. | 2 / 3 |
Progressive Disclosure | References related skills at the end but the main content is a monolithic document with extensive inline code that could be split into separate reference files (e.g., code-patterns.md, testing.md). The 'Related Skills' section is good but underutilized. | 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
- duclm1x1/Dive-Ai
- Commit
20ba150
- 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.