fullstack-guardian
Builds security-focused full-stack web applications by implementing integrated frontend and backend components with layered security at every level. Covers the complete stack from database to UI, enforcing auth, input validation, output encoding, and parameterized queries across all layers. Use when implementing features across frontend and backend, building REST APIs with corresponding UI, connecting frontend components to backend endpoints, creating end-to-end data flows from database to UI, or implementing CRUD operations with UI forms. Distinct from frontend-only, backend-only, or API-only skills in that it simultaneously addresses all three perspectives—Frontend, Backend, and Security—within a single implementation workflow. Invoke for full-stack feature work, web app development, authenticated API routes with views, microservices, real-time features, monorepo architecture, or technology selection decisions.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that excels across all dimensions. It provides comprehensive specificity with concrete actions, includes abundant natural trigger terms, explicitly addresses both what and when, and clearly differentiates itself from related skills. The description is thorough without being padded with fluff.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'implementing integrated frontend and backend components', 'enforcing auth, input validation, output encoding, and parameterized queries', 'building REST APIs', 'connecting frontend components to backend endpoints', 'creating end-to-end data flows', 'implementing CRUD operations with UI forms'. | 3 / 3 |
Completeness | Clearly answers both what (builds security-focused full-stack web apps with layered security) AND when with explicit 'Use when...' clause listing specific triggers like 'implementing features across frontend and backend', 'building REST APIs with corresponding UI', plus additional 'Invoke for...' guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'full-stack', 'web applications', 'REST APIs', 'frontend', 'backend', 'CRUD operations', 'UI forms', 'microservices', 'real-time features', 'monorepo', 'authenticated API routes'. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from 'frontend-only, backend-only, or API-only skills' and carves out a clear niche for simultaneous multi-layer implementation with security focus. The combination of full-stack + security integration creates a distinct identity. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently covers full-stack security-focused development. It excels at progressive disclosure through its reference table, provides concrete executable examples across all three perspectives, and maintains a clear workflow with security checkpoints. The constraints section effectively communicates boundaries without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose—workflow, reference table, constraints, and example are all actionable without padding. | 3 / 3 |
Actionability | Provides fully executable Python and TypeScript code examples demonstrating the three-perspective approach. The constraints are specific and actionable (parameterized queries, sanitize output), and the reference table gives clear guidance on when to load each resource. | 3 / 3 |
Workflow Clarity | The 6-step core workflow is clearly sequenced with an explicit security checkpoint before coding. The MUST DO/MUST NOT DO constraints provide validation guidance, and the workflow includes testing each component incrementally. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, well-organized reference table pointing to 10 separate documents with clear 'Load When' guidance, and a single concrete example. References are one level deep and clearly signaled. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
5b76101
- Reviewed
Table of Contents
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.