agent-project-guidelines-example
Project Guidelines Skill (Example)
33
Quality
14%
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 ./.agent/skills/agent-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
29%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions well as a project overview and navigation hub with good progressive disclosure, but it lacks actionable content of its own. The architecture diagram and file structure are informative but passive—there are no concrete instructions, code examples, or workflows that Claude can execute directly from this document.
Suggestions
Add at least one executable code example in the main skill (e.g., a quick-start command to run the project locally or a minimal API call example)
Include a basic workflow for common tasks (e.g., 'Adding a new feature: 1. Create route in backend/routers, 2. Add Pydantic model, 3. Create frontend hook, 4. Test with pytest')
Remove or condense the meta-commentary ('This is an example...', 'Use this as a template...') which doesn't help Claude perform tasks
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary framing ('This is an example...', 'Based on a real production application') and the 'When to Use' section explains what project skills contain, which is meta-information Claude doesn't need. | 2 / 3 |
Actionability | The skill provides no executable code, commands, or concrete guidance. It describes architecture and file structure but offers no actionable instructions—everything concrete is deferred to sub-skills via links. | 1 / 3 |
Workflow Clarity | No workflows are defined in this document. The 'Code Patterns' section is just a list of links to sub-skills with no sequencing, validation steps, or process guidance. | 1 / 3 |
Progressive Disclosure | The skill appropriately serves as an overview with clear, well-organized references to sub-skills. Links are one level deep, clearly labeled by topic, and the structure enables easy navigation to detailed content. | 3 / 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
- Dokhacgiakhoa/antigravity-ide
- Commit
3395991
- 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.