cc-skill-project-guidelines-example

tessl i github:sickn33/antigravity-awesome-skills --skill cc-skill-project-guidelines-example

Project Guidelines Skill (Example)

49%

Overall

Validation — 75%

Implementation — 65%

Activation — 0%

SKILL.md

Review

Evals

Validation

75%

Warnings & errors only

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	12 / 16 Passed

Implementation

65%

This is a solid project guidelines template with excellent actionable code examples and clear structure. However, it's verbose for a SKILL.md overview—much of the detailed code patterns and testing examples should be in referenced files. The deployment workflow lacks validation checkpoints and error recovery guidance.

Suggestions

Move detailed code patterns (API response format, hooks, Claude integration) to a separate PATTERNS.md file and reference it from the overview

Add explicit validation steps to the deployment workflow: 'If build fails, check X. If deploy fails, run Y to diagnose'

Remove the 'When to Use' section—Claude understands when to reference project-specific skills

Add a quick-reference section at the top with the most critical commands and patterns, keeping detailed examples in linked files

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary verbosity like the 'When to Use' section explaining what project skills contain (Claude knows this). The architecture diagram and code examples are useful but could be tighter.	2 / 3
Actionability	Provides fully executable code examples for API responses, frontend calls, Claude integration, custom hooks, and tests. Commands are copy-paste ready with specific paths and flags.	3 / 3
Workflow Clarity	Deployment workflow has a checklist and commands, but lacks explicit validation checkpoints and feedback loops. No 'if deployment fails, do X' recovery steps. Testing section shows commands but doesn't integrate into a clear workflow.	2 / 3
Progressive Disclosure	References related skills at the end but the main content is a monolithic document with extensive inline code that could be split into separate reference files (e.g., code-patterns.md, testing.md). The 'Related Skills' section is good but underutilized.	2 / 3
	Total	9 / 12 Passed

Activation

This description is essentially a placeholder or title rather than a functional skill description. It provides no information about capabilities, use cases, or trigger conditions, making it impossible for Claude to determine when to select this skill from a library of options.

Suggestions

Add specific concrete actions describing what this skill does (e.g., 'Enforces coding standards, validates project structure, checks naming conventions')

Include an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about project standards, coding guidelines, style rules, or conventions')

Remove the '(Example)' qualifier and specify what type of project guidelines this covers to distinguish it from other potential guideline-related skills

Dimension	Reasoning	Score
Specificity	The description 'Project Guidelines Skill (Example)' contains no concrete actions whatsoever - it merely names itself with a generic label and '(Example)' qualifier, providing zero information about what it actually does.	1 / 3
Completeness	Fails to answer both 'what does this do' and 'when should Claude use it' - there is no description of capabilities and no 'Use when...' clause or equivalent guidance.	1 / 3
Trigger Term Quality	Contains no natural keywords users would say. 'Project Guidelines' is vague and 'Skill (Example)' is meta-language about the skill itself rather than trigger terms for when to use it.	1 / 3
Distinctiveness Conflict Risk	Extremely generic - 'Project Guidelines' could conflict with any skill related to projects, documentation, standards, coding conventions, or organizational rules. No distinct triggers to differentiate it.	1 / 3
	Total	4 / 12 Passed

Reviewed

19 days ago

Table of Contents

Validation Implementation Activation

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.