cc-skill-project-guidelines-example

Project Guidelines Skill (Example)

Quality

42%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/cc-skill-project-guidelines-example/SKILL.md

The canonical home for this skill is cc-skill-project-guidelines-example in sickn33/agentic-awesome-skills

Quality

Content

68%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 well-structured, mostly actionable project-guidelines reference with executable code across the stack. Its main weaknesses are the lack of a validation feedback loop in the deployment workflow and the absence of any progressive disclosure into separate bundle files.

Suggestions

Add an explicit validation checkpoint to the deployment workflow, e.g. 'Run npm run build and poetry run pytest; only proceed to gcloud run deploy when both pass; if either fails, fix and re-run.'

Move the detailed code-pattern catalog into separate reference files (e.g. references/code-patterns.md) and keep SKILL.md as an overview pointing to them, improving progressive disclosure.

Trim the example/template framing prose and fictional component examples so every token earns its place.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean: architecture diagrams, a file tree, and executable code patterns with little over-explanation of concepts Claude already knows, matching the 'efficient; minor instances that could be trimmed' anchor (4) rather than the lean-every-token-earns-its-place anchor (5) because the example/template framing adds some non-essential prose.	4 / 5
Actionability	It provides concrete, copy-paste-ready code for FastAPI responses, frontend fetch wrappers, Claude structured output, React hooks, and pytest/RTL tests, matching 'mostly executable guidance; minor gaps' (4); it stops short of 5 because some examples use fictional component names and illustrative env values.	4 / 5
Workflow Clarity	The deployment section lists a pre-deployment checklist and commands but has no explicit validate-then-proceed feedback loop for a batch/destructive operation, which the rubric caps at 3; it is above 2 because a checklist and rough sequence are present.	3 / 5
Progressive Disclosure	No bundle files exist, and the content is a single well-organized file with clear section headers and a Related Skills pointer, matching 'good structure; references mostly clear; minor organization gaps' (4); it is not 5 because large blocks of code patterns that could live in separate reference files are all inlined.	4 / 5
	Total	15 / 20 Passed

Description

16%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 just a title with no statement of capabilities or trigger conditions, failing to tell Claude when to invoke it or what it does. It needs concrete actions and an explicit 'Use when...' clause.

Suggestions

Replace the title-only description with concrete actions, e.g. 'Documents architecture, file structure, code patterns, and deployment workflow for the Zenith project.'

Add an explicit trigger clause such as 'Use when working on the Zenith codebase, deploying to Cloud Run, or following project-specific coding standards.'

Use third person and include natural trigger terms users would actually say (project guidelines, Zenith, Cloud Run deploy) to improve distinctiveness.

Dimension	Reasoning	Score
Specificity	The description 'Project Guidelines Skill (Example)' names the domain but states no concrete actions at all, sitting between the entirely-vague anchor (1) and the domain-with-minimal-actions anchor (2); it names the domain so it is above 1, but lacks any named action so it cannot reach 3.	2 / 5
Completeness	It answers neither 'what does this do' (no actions) nor 'when should Claude use it' (no 'Use when...' clause), which is the missing-both anchor (1); it cannot be 2 because there is not even a vague 'what' or 'when' present.	1 / 5
Trigger Term Quality	Only the generic phrase 'Project Guidelines' appears, with no natural trigger phrasing a user would actually say; this matches the 'one or two generic keywords' anchor (2) and is clearly below the 'some relevant keywords' anchor (3).	2 / 5
Distinctiveness Conflict Risk	'Project Guidelines Skill' is very broad and would overlap with many general coding-standards or project skills, matching the 'very broad; high overlap risk' anchor (2) rather than the entirely-generic anchor (1).	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/cc-skill-project-guidelines-example/SKILL.md
Commit: 57c135b

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