cc-skill-project-guidelines-example

Project Guidelines Skill (Example)

Quality

25%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/cc-skill-project-guidelines-example/SKILL.md

Quality

Discovery

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 trigger terms, e.g., 'Use when the user asks about project conventions, coding standards, style guidelines, or repository structure.'

Include specific file types, tools, or domains to make the skill distinctive and reduce conflict risk with other skills.

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, not 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

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is highly actionable with excellent concrete code examples and commands, but suffers significantly from verbosity — it includes full boilerplate patterns (generic API responses, fetch wrappers, React hooks) that Claude can generate from brief descriptions. The file structure and architecture diagram are useful but could be much more concise. Progressive disclosure is underutilized; the bulk of code patterns and test examples should live in referenced files.

Suggestions

Drastically reduce code examples to project-specific conventions only (e.g., 'Use ApiResponse.ok()/fail() pattern' with a 3-line snippet), moving full implementations to referenced files like backend-patterns.md

Add post-deployment validation steps (e.g., 'Verify: curl https://api.example.com/health returns 200') and error recovery guidance to the deployment workflow

Split code patterns, testing examples, and deployment details into the referenced files (backend-patterns.md, frontend-patterns.md, etc.) and keep only summaries with links in the main skill

Remove explanations of standard patterns Claude already knows (generic TypeVar response classes, basic fetch wrappers, standard pytest fixtures) and focus on project-specific deviations

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~250+ lines. The architecture diagram, full file tree, and multiple complete code examples (API response class, fetch wrapper, custom hooks, Claude integration, test fixtures) are extensive boilerplate that Claude already knows how to write. Much of this could be condensed to key patterns and conventions unique to the project.	1 / 3
Actionability	Provides fully executable, copy-paste ready code examples across Python and TypeScript, concrete test commands, deployment commands, and specific environment variable templates. Every section contains actionable, concrete guidance.	3 / 3
Workflow Clarity	The deployment section has a checklist and sequential commands, but lacks explicit validation checkpoints and feedback loops (e.g., what to do if `gcloud run deploy` fails, no post-deployment verification step). Testing workflow is clear but deployment workflow has gaps.	2 / 3
Progressive Disclosure	References related skills at the bottom (coding-standards.md, backend-patterns.md, etc.), but the main file is monolithic with extensive inline code that could be split into referenced files. The architecture overview, code patterns, and testing sections each warrant their own files with summaries in the main skill.	2 / 3
	Total	8 / 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: sickn33/antigravity-awesome-skills
Commit: 6a07b83

Reviewed: 4 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.