fullstack-guardian

Name: fullstack-guardian
Rating: 67 (1 reviews)
Author: jeffallan

tessl i github:jeffallan/claude-skills --skill fullstack-guardian

github.com/jeffallan/claude-skills

Use when implementing features across frontend and backend, building APIs with UI, or creating end-to-end data flows. Invoke for feature implementation, API development, UI building, cross-stack work.

Review Score

67%

Validation Score

12/16

Implementation Score

57%

Activation Score

67%

SKILL.md

Review

Evals

Generated

13 days ago

Warnings & errors only

Criteria	Score
metadata_version	'metadata' field is not a dictionary
license_field	'license' field is missing
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata
body_examples	No examples detected (no code fences and no 'Example' wording)

Overall Assessment

This skill provides good structural organization with excellent progressive disclosure through its reference table, but falls short on actionability by lacking concrete code examples for the security patterns it emphasizes. The workflow is clear but missing validation checkpoints critical for security-focused development. The content would benefit from executable examples demonstrating the security practices it mandates.

Suggestions

Add concrete code examples for critical security patterns (parameterized queries, input validation, output sanitization) in the main file or clearly indicate which reference contains them
Insert explicit validation checkpoints in the Core Workflow, e.g., 'Review security checklist before step 4' and 'Verify all MUST DO items before handoff'
Remove or condense the 'When to Use This Skill' section as it largely repeats the description and adds little actionable value

Dimension	Score	Reasoning
Conciseness	2/3	The skill is reasonably efficient but includes some unnecessary framing ('You are a senior full-stack engineer with 12+ years of experience') and the 'When to Use This Skill' section largely duplicates information Claude could infer. The reference table is well-organized but the overall content could be tighter.
Actionability	2/3	Provides clear constraints (MUST DO/MUST NOT DO) and a workflow, but lacks concrete code examples or executable commands. The guidance is specific in principle but abstract in practice - no actual code snippets for validation, parameterized queries, or error handling patterns.
Workflow Clarity	2/3	The 5-step core workflow is clearly sequenced, but lacks validation checkpoints between steps. For a skill involving security-critical operations, there's no explicit 'verify security checklist before proceeding' or feedback loops for catching issues before handoff.
Progressive Disclosure	3/3	Excellent use of reference table with clear 'Load When' guidance. Content is appropriately split between overview in main file and detailed guidance in referenced files. Navigation is clear and references are one level deep.

Overall Assessment

The description has good structural completeness with explicit 'Use when' and 'Invoke for' clauses, which is a strength. However, it lacks concrete specific actions and relies on somewhat generic terminology that could overlap with more specialized skills. The description would benefit from more specific examples of cross-stack work and additional natural trigger terms.

Suggestions

Add more concrete actions like 'connect frontend components to backend endpoints', 'implement database-to-UI data flows', or 'build authenticated API routes with corresponding UI'
Include additional natural trigger terms users might say: 'full-stack', 'web app', 'REST API with frontend', 'server and client', 'database integration'

Dimension	Score	Reasoning
Specificity	2/3	Names domain (frontend/backend, APIs, UI) and mentions some actions (implementing features, building APIs, creating data flows), but lacks concrete specific actions like 'create REST endpoints', 'connect React components to backend services', or 'implement database queries with UI forms'.
Completeness	3/3	Explicitly answers both what (implementing features across frontend/backend, building APIs with UI, creating end-to-end data flows) and when (Use when... Invoke for...) with clear trigger guidance.
Trigger Term Quality	2/3	Includes some relevant terms like 'API', 'UI', 'frontend', 'backend', 'cross-stack', but missing common variations users might say like 'full-stack', 'server and client', 'REST', 'database', 'web app', or specific framework names.
Distinctiveness Conflict Risk	2/3	The 'cross-stack' and 'end-to-end' framing provides some distinction, but terms like 'API development', 'UI building', and 'feature implementation' are generic enough to potentially conflict with dedicated frontend, backend, or API-specific skills.