cc-skill-project-guidelines-example

Project Guidelines Skill (Example)

Quality

44%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

63%Weight 40%Scale 1-5

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

The content is a strong, actionable project-conventions reference with executable code and a validated deployment workflow, but it is monolithic with no progressive disclosure into reference files and carries some generic advice and meta-commentary that dilute conciseness.

Suggestions

Split the code-pattern and testing sections into one-level-deep reference files (e.g. references/code-patterns.md, references/testing.md) referenced from the overview to improve progressive disclosure.

Trim the generic 'Critical Rules' list and the 'Use this as a template' meta-commentary, keeping only project-specific conventions Claude would not already know.

Fix the minor actionability gaps: parameterize the model id and use the async Anthropic client (or await) inside analyze_with_claude.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete, project-specific code, but includes unnecessary meta-commentary ('Use this as a template for your own projects') and a 'Critical Rules' section of generic advice Claude already knows (no console.log, immutability, TDD), so it could be tightened.	3 / 5
Actionability	It provides copy-paste-ready, executable code for ApiResponse, fetchApi, the useApi hook, Claude tool-calling integration, plus concrete pytest/gcloud commands, with only minor gaps such as a hardcoded model id and a sync Anthropic client used inside an async function.	4 / 5
Workflow Clarity	The deployment workflow gives a clear sequence with a pre-deployment validation checklist ('All tests passing', 'npm run build succeeds', 'poetry run pytest passes') followed by explicit commands, satisfying the validation requirement though it lacks an explicit fix-and-retry feedback loop.	4 / 5
Progressive Disclosure	The body is well-sectioned but monolithic: no bundle files exist (references/, scripts/, assets/ are absent) and all code patterns and references are inlined, while the over-50-line skill would benefit from splitting detail into one-level-deep reference files.	3 / 5
	Total	14 / 20 Passed

Description

25%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is essentially a title: it names the domain but provides no concrete actions, no natural trigger terms, and no explicit when-to-use guidance. It would rarely be selected correctly on description alone.

Suggestions

Rewrite the description to state concrete actions, e.g. 'Applies Zenith project conventions: FastAPI/Next.js patterns, ApiResponse wrappers, pytest and Playwright testing, and Cloud Run deployment.

Add an explicit 'Use when...' trigger clause naming the project and the situations that call for it (e.g. 'Use when working on the Zenith codebase or its architecture, file structure, and deployment workflow').

Include natural user phrases and distinguishing terms (project name, tech stack) to lower conflict risk with other project-guideline skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Project Guidelines Skill (Example)' names the domain but states no concrete actions whatsoever, fitting the 'names the domain but actions are minimal or generic' anchor better than the entirely-vague anchor 1 since it is not pure abstract filler.	2 / 5
Completeness	It provides only a vague label as the 'what' and gives no 'when' trigger guidance at all, sitting at the 'has a vague what and no when' anchor; the missing Use-when clause also caps completeness at 3, which is not reached.	2 / 5
Trigger Term Quality	It offers only the generic keyword 'Project Guidelines' with no natural user phrases such as 'when working on the Zenith project' or 'project conventions', matching the 'one or two generic keywords; missing the natural phrases users say' anchor.	2 / 5
Distinctiveness Conflict Risk	'Project Guidelines Skill' is very broad and would overlap with any other project-specific guideline skill, matching the 'very broad; high overlap risk with many similar skills' anchor rather than the fully generic anchor 1.	2 / 5
	Total	8 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/cc-skill-project-guidelines-example/SKILL.md
Commit: 1f67c44

Reviewed: about 15 hours 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.