agent-project-guidelines-example
Project Guidelines Skill (Example)
28
11%
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 no information about what the skill does, when to use it, or how it differs from other skills. It fails all evaluation criteria and would be unusable for skill selection in a multi-skill environment.
Suggestions
Add concrete actions describing what this skill does (e.g., 'Enforces project coding standards, validates file structure, checks naming conventions').
Include an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks about project rules, coding standards, style guidelines, or best practices').
Specify the domain or context to distinguish from other skills (e.g., 'for Python projects' or 'for this repository's contribution 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. Provides no distinguishing characteristics. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a structural template and navigation hub rather than actionable guidance. While it provides useful architecture diagrams and file structure, it lacks any concrete instructions, code examples, or workflows. The content delegates everything to sub-skills without providing a usable quick-start or summary of key actions.
Suggestions
Add a 'Quick Start' section with 2-3 concrete commands to get the project running locally (e.g., `npm install`, `docker-compose up`, environment setup)
Include at least one executable code example demonstrating a core pattern (e.g., a sample API endpoint or component)
Add a basic workflow for common tasks like 'Adding a new feature' with numbered steps and validation checkpoints
Remove or condense the meta-commentary ('This is an example...', 'When to Use' explanation) to focus on actionable content
| 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 lacks any actionable instructions—everything is delegated to sub-skills without even summarizing what actions to take. | 1 / 3 |
Workflow Clarity | No workflows are defined in this skill. The 'Code Patterns' section is just a list of links with no sequencing, validation steps, or process guidance. There's no indication of how to actually work on this project. | 1 / 3 |
Progressive Disclosure | The skill does reference sub-skills appropriately (one level deep), but the main content lacks a quick-start or actionable overview. The sub-skill links are well-organized but the parent skill provides no usable content itself—it's almost entirely a table of contents. | 2 / 3 |
Total | 6 / 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
332e58b
- 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.