CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fullstack-dev

Full-stack backend architecture and frontend-backend integration guide. TRIGGER when: building a full-stack app, creating REST API with frontend, scaffolding backend service, building todo app, building CRUD app, building real-time app, building chat app, Express + React, Next.js API, Node.js backend, Python backend, Go backend, designing service layers, implementing error handling, managing config/auth, setting up API clients, implementing auth flows, handling file uploads, adding real-time features (SSE/WebSocket), hardening for production. DO NOT TRIGGER when: pure frontend UI work, pure CSS/styling, database schema only.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with clear validated workflows and well-organized references, but its large inline volume works against conciseness and the progressive-disclosure ideal of a lean overview.

Suggestions

Move the longer pattern sections (e.g., API Client Patterns, Real-Time Patterns, File Upload) into reference files and keep only a one-line summary plus a link in SKILL.md to reduce the inline footprint.

Trim interpretive prose like "The 'glue layer' between frontend and backend" and "Best for:" lead-ins, keeping only the concrete pattern, code, and decision table.

Consolidate the duplicate navigations (Quick Navigation table, Reference Documents table, and in-line reference links) into a single index to cut repeated tokens.

DimensionReasoningScore

Conciseness

The body is dense with executable code and rules, but at roughly 1000 lines it includes explanatory prose ("The 'glue layer' between frontend and backend", "Best for: notifications...") and inline bulk that could be tightened to respect the context budget.

2 / 3

Actionability

It provides extensive copy-paste-ready TypeScript/Python/Go code, concrete commands (npm run build, alembic, migrate, openapi codegen), and decision tables that give fully executable guidance.

3 / 3

Workflow Clarity

A "MANDATORY WORKFLOW — Follow These Steps In Order" sequences Steps 0–5, with Step 4 build/smoke/integration checks and an explicit feedback loop ("If any check fails, fix the issue before proceeding") plus checklists.

3 / 3

Progressive Disclosure

Navigation tables and 8 real one-level-deep reference files are well signaled, but 13 detailed inline sections (full code for API clients, real-time, error handling) make SKILL.md itself a monolithic reference rather than a lean overview deferring detail to the bundle.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 specific, trigger-rich, and complete, clearly stating both capabilities and when to activate while carving out a distinct full-stack niche with explicit exclusions.

DimensionReasoningScore

Specificity

The description lists many concrete actions such as "scaffolding backend service", "implementing auth flows", "handling file uploads", and "adding real-time features (SSE/WebSocket)" rather than vague language.

3 / 3

Completeness

It states what ("Full-stack backend architecture and frontend-backend integration guide") and gives an explicit "TRIGGER when:" clause plus a "DO NOT TRIGGER when" exclusion, answering both what and when.

3 / 3

Trigger Term Quality

It covers natural terms users would say — "building todo app", "building CRUD app", "Express + React", "Next.js API", "Node.js/Python/Go backend" — with strong variation across stacks.

3 / 3

Distinctiveness Conflict Risk

The full-stack integration niche is bounded by explicit exclusions ("pure frontend UI work, pure CSS/styling, database schema only"), making conflict with adjacent skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1038 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

MiniMax-AI/skills

Path

skills/fullstack-dev/SKILL.md

Revision

60aaae5

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill