cc-skill-project-guidelines-example
Project Guidelines Skill (Example)
28
21%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./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 label with no functional content. It fails on every dimension: it provides no concrete actions, no trigger terms, no guidance on when to use it, and nothing to distinguish it from other skills. It appears to be an example stub rather than a real skill description.
Suggestions
Replace the placeholder with a concrete description of what the skill does, e.g., 'Reads and applies project-specific coding standards, naming conventions, and architectural guidelines from configuration files.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about project conventions, coding standards, style guides, or project-specific rules.'
Include specific file types, formats, or artifacts the skill works with to improve distinctiveness, e.g., '.editorconfig, .eslintrc, CONTRIBUTING.md, or project README files.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description 'Project Guidelines Skill (Example)' provides no concrete actions whatsoever. It names a vague domain ('Project Guidelines') but describes nothing about what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause or any equivalent guidance for skill selection. | 1 / 3 |
Trigger Term Quality | There are no natural keywords a user would say. 'Project Guidelines' is generic and '(Example)' suggests this is a placeholder rather than a real description. No actionable trigger terms are present. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic and could conflict with any skill related to projects, guidelines, documentation, or standards. There is nothing to distinguish it from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a comprehensive but overly verbose project reference that dumps everything into a single file rather than serving as a concise overview with progressive disclosure. While the code examples are high-quality and executable, much of the content covers standard patterns Claude already knows (generic API responses, fetch wrappers, React hooks, pytest fixtures). The deployment workflow lacks validation feedback loops, and the referenced related skills don't exist as bundle files.
Suggestions
Extract code patterns, testing examples, and deployment details into separate referenced files (e.g., PATTERNS.md, TESTING.md, DEPLOY.md) and keep SKILL.md as a concise overview with navigation links.
Remove or drastically shorten standard patterns Claude already knows (generic API response classes, fetch wrappers, custom hooks) and focus only on project-specific conventions that deviate from common practice.
Add explicit validation and rollback steps to the deployment workflow: verify health endpoint after deploy, rollback command if smoke test fails, and integrate the checklist as sequential gated steps.
Create the referenced bundle files (coding-standards.md, backend-patterns.md, frontend-patterns.md, tdd-workflow/) or remove the references to avoid dead links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines. It explains basic concepts Claude already knows (what App Router is, how fetch works, generic API response patterns), includes full boilerplate code for standard patterns (custom hooks, test fixtures, API wrappers), and the architecture diagram adds visual bulk without project-specific insight. Much of this is general full-stack development knowledge that doesn't need to be spelled out. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples across Python, TypeScript, and bash. Commands for testing, deployment, and environment setup are concrete and specific. Code patterns include complete implementations with imports and type annotations. | 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' recovery step, no verification after deployment (e.g., smoke test the endpoint), and the pre-deployment checklist is disconnected from the deployment commands rather than integrated as sequential validated steps. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic wall of text with all content inline. The 'Related Skills' section references files like `coding-standards.md` and `backend-patterns.md`, but no bundle files exist to support them. The massive code patterns section, testing section, and deployment section should each be in separate referenced files, with SKILL.md serving as a concise overview. | 1 / 3 |
Total | 7 / 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
- sickn33/antigravity-awesome-skills
- Commit
fb2efea
- 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.