cc-skill-project-guidelines-example

Project Guidelines Skill (Example)

Quality

49%

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

78%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 body is a strong, highly actionable project reference with executable commands and complete code patterns, weakened mainly by structure: everything is inlined in one large file and the Related Skills references point to non-existent files. Adding a post-deploy verification step would round out the workflow.

Suggestions

Move the four code-pattern sections and the testing structures into reference files (e.g. references/patterns.md, references/testing.md) and keep SKILL.md as an overview with one-level-deep, clearly signaled links.

Fix or remove the 'Related Skills' links — coding-standards.md, backend-patterns.md, frontend-patterns.md, and tdd-workflow/ do not exist in this bundle.

Add a post-deployment validation step (e.g. curl the /health endpoint or check the Cloud Run revision) to close the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, high-value code and commands with little explanation of concepts Claude already knows; it falls short of 5 because of the meta 'use this as a template' framing, the illustrative env-var block, and time-sensitive version pins ('claude-sonnet-4-5-20250514', Next.js 15, Python 3.11) placed outside any deprecated-patterns section.	4 / 5
Actionability	Commands are copy-paste ready ('poetry run pytest tests/ --cov=.', 'gcloud run deploy backend --source .', 'npm run test:e2e') and every code pattern (ApiResponse, fetchApi, useApi, Claude structured-output tool use, test structures) is complete and executable, covering the common cases with no pseudocode or missing key details.	5 / 5
Workflow Clarity	The deployment workflow presents a clear pre-flight checklist (tests passing, build succeeds, no hardcoded secrets, migrations ready) followed by ordered build/deploy commands, but it lacks a post-deploy verification checkpoint such as hitting the /health endpoint, keeping it below the explicit feedback-loop standard of anchor 5.	4 / 5
Progressive Disclosure	Section headers are clear, but roughly 350 lines inline everything — code patterns, testing structures, and deployment details that belong in separate reference files — and the 'Related Skills' links (coding-standards.md, backend-patterns.md, frontend-patterns.md, tdd-workflow/) point to files that do not exist in the bundle; it is well-sectioned enough to stay above the wall-of-text anchors.	3 / 5
	Total	16 / 20 Passed

Description

20%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 effectively just a title. It names a generic domain but describes no capabilities, includes no trigger terms, and gives no guidance on when to use the skill, making it indistinguishable from other project-guidelines skills.

Suggestions

Rewrite the description to list concrete capabilities, e.g. 'Provides architecture overview, file structure, code patterns, testing requirements, and deployment workflow for the Zenith project' (drawn from the body's own 'Project skills contain' list).

Add an explicit 'Use when...' clause, e.g. 'Use when working on the Zenith codebase, modifying FastAPI routers or Next.js components, or preparing a Cloud Run deployment.'

Include project-specific trigger terms (Zenith, Supabase, Cloud Run, gcloud run deploy) so the skill is distinguishable from generic coding-standards skills.

Dimension	Reasoning	Score
Specificity	The description 'Project Guidelines Skill (Example)' is a bare title with no action verbs or concrete capabilities — pure abstract labeling, matching the 'no concrete actions' anchor rather than anchor 2, which at least names an action like 'Processes PDF files'.	1 / 5
Completeness	It has only a vague 'what' (a named skill category) and no 'when' clause whatsoever, fitting the 'vague what and no when' anchor; it is not anchor 1 because a domain is at least named, and cannot reach 3-4 since no use-when guidance exists even weakly.	2 / 5
Trigger Term Quality	'Project Guidelines' is one generic keyword with no natural trigger phrases a user would say when needing this skill; it is not technical jargon (ruling out 1), but it misses the common variations and synonyms that anchor 4 expects.	2 / 5
Distinctiveness Conflict Risk	'Project Guidelines Skill' is very broad and does not identify which project, so it would overlap with virtually any coding-standards or conventions skill; it lacks the niche triggers needed for 4-5.	2 / 5
	Total	7 / 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/agentic-awesome-skills
Path: skills/cc-skill-project-guidelines-example/SKILL.md
Commit: 7b534bc

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