agent-project-guidelines-example

Project Guidelines Skill (Example)

Quality

11%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/agent-project-guidelines-example/SKILL.md

Quality

Content

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 more as a project README than an actionable skill for Claude. It provides useful structural context (tech stack, file layout, architecture diagram) but lacks any concrete, executable guidance — all actionable content is deferred to sub-skills that cannot be verified. The meta-framing as a 'template' and 'example' adds unnecessary tokens without helping Claude perform any specific task.

Suggestions

Add at least one concrete, executable code example inline for the most common patterns (e.g., a FastAPI endpoint example, a frontend API call example) rather than deferring everything to sub-skills.

Remove the meta-framing ('This is an example...', 'Use this as a template...', 'Based on a real production application') which wastes tokens and doesn't help Claude perform tasks.

Add a workflow section with explicit steps and validation checkpoints for at least one key process (e.g., adding a new feature end-to-end, or the deployment process).

Include the bundle sub-skill files so the progressive disclosure structure actually works, or inline the most critical patterns from those sub-skills.

Dimension	Reasoning	Score
Conciseness	The content includes some unnecessary framing ('This is an example of a project-specific skill. Use this as a template...') and the 'When to Use' section explains what project skills contain, which is meta-information Claude doesn't need. The architecture diagram and file structure are useful but could be tighter. The 'Based on a real production application' line is unnecessary filler.	2 / 3
Actionability	The skill provides no executable code, no concrete commands, and no specific instructions for any task. It describes architecture and file structure but never tells Claude what to actually do. The code patterns section is entirely delegated to sub-skills with no inline examples or guidance.	1 / 3
Workflow Clarity	There are no workflows defined in this skill. No multi-step processes, no validation checkpoints, no sequenced operations. The 'Code Patterns' section which could contain workflow guidance is entirely empty except for links to sub-skills. Even the deployment and testing workflows are fully deferred.	1 / 3
Progressive Disclosure	The skill does reference 9 sub-skills with clear one-level-deep links, which is good structure. However, since no bundle files are provided, we cannot verify these references exist. The main skill itself is somewhat monolithic with the architecture diagram and file structure inline, while the code patterns section is entirely empty — an imbalanced split where the overview has too much static reference material and too little actionable content.	2 / 3
	Total	6 / 12 Passed

Description

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 'when to use' guidance, and no distinguishing characteristics. It would be unusable for skill selection in a multi-skill environment.

Suggestions

Replace the placeholder with a concrete description of what the skill does, e.g., 'Enforces project-specific coding standards, naming conventions, and directory structure rules when generating or reviewing code.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about project conventions, coding standards, style guidelines, or repository structure.'

Include specific file types, actions, or domains to make the skill clearly distinguishable from other skills, e.g., 'Reads .editorconfig, linting configs, and CONTRIBUTING.md to apply project-specific rules.'

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

Validation

90%

Warnings & errors only

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: c4a059b

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

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.