CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./configs/microservice/bff-service/configs/agent-skills/minimax/fullstack-dev/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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.

A well-structured, highly actionable full-stack reference with an exemplary mandatory workflow and clean one-level-deep references. Its main liability is token efficiency: the 1051-line body restates the same rules across checklists, iron rules, per-section rules, and an anti-patterns table, and inlines content that belongs in the existing reference files.

Suggestions

Consolidate the duplicated rule statements (Quick Start checklists, '7 Iron Rules', per-section ✅/❌ blocks, and the 18-row Anti-Patterns table) into a single source of truth, keeping only one compact summary form — this alone would cut hundreds of lines.

Move the full implementation listings for lower-frequency topics (Section 10 File Uploads, Section 11 Real-Time, Section 5 API Client Options C/D) into reference files alongside the existing 8, keeping only the decision tables and one minimal example inline in SKILL.md.

Trim educational boilerplate Claude already knows — the three-language dependency-injection skeletons, the log-level table, and the layer-responsibility prose — down to one-line rules.

DimensionReasoningScore

Conciseness

At 1051 lines, the body repeats the same guidance up to four times — the two Quick Start checklists, the '7 Iron Rules', per-section ✅/❌ rule blocks, and the 18-row Anti-Patterns table all restate the same rules — and includes padded boilerplate Claude already knows (dependency-injection class skeletons in three languages, log-level tables). This is noticeably verbose per anchor 2; not anchor 1 because the material is not concept-explanation filler throughout, and not anchor 3 because the redundancy is pervasive rather than occasional.

2 / 5

Actionability

Most guidance is concrete and executable: full Express global error handler, typed fetch client, tRPC router, React Query hooks with cache invalidation, ws WebSocket server, and a complete presigned-URL upload flow. Minor gaps keep it below anchor 5 — several examples depend on undefined helpers (handleMessage, eventBus, checkDb, drainConnections, getAuthToken) and reconnect callbacks are left as /* reconnect */ placeholders.

4 / 5

Workflow Clarity

The mandatory workflow (Steps 0-5) is clearly sequenced with explicit validation checkpoints: exact build commands (npm run build), smoke-test commands (curl /health, /api/<resource>), an integration check, a real-time two-tab check, and an explicit feedback loop ("If any check fails, fix the issue before proceeding"), plus decision tables and a handoff summary — matching anchor 5.

5 / 5

Progressive Disclosure

Structure is good: a Quick Navigation table and a Reference Documents table point to all 8 real, one-level-deep reference files (api-design.md, db-schema.md, auth-flow.md, environment-management.md, testing-strategy.md, release-checklist.md, technology-selection.md, django-best-practices.md), clearly signaled by task. Below anchor 5 because substantial deep-dive content (full real-time implementations, file-upload flows, API-client options) is inlined in SKILL.md itself rather than split into the reference layer.

4 / 5

Total

15

/

20

Passed

Description

91%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.

A strong description with an explicit and comprehensive TRIGGER/DO-NOT-TRIGGER structure covering natural user phrasings, stack names, and synonyms. The main weakness is that the capability statement itself is a generic 'guide' phrase, leaving the concrete actions to live only in the trigger list.

DimensionReasoningScore

Specificity

The trigger list names many concrete actions ("scaffolding backend service", "implementing auth flows", "handling file uploads", "adding real-time features (SSE/WebSocket)", "hardening for production"), but the opening 'what' statement is generic ("Full-stack backend architecture and frontend-backend integration guide") rather than enumerating the skill's own capabilities. This sits above anchor 3 (only 1-2 concrete actions) and below anchor 5 (comprehensive concrete action coverage in the capability statement itself).

4 / 5

Completeness

Explicitly answers both 'what' ("Full-stack backend architecture and frontend-backend integration guide") and 'when' with a concrete TRIGGER clause listing ~20 trigger phrases, plus a DO NOT TRIGGER exclusion clause — matching anchor 5's requirement for clear what AND when with concrete triggers.

5 / 5

Trigger Term Quality

Covers natural user phrasing ("building todo app", "building CRUD app", "building chat app"), stack-specific terms ("Express + React", "Next.js API", "Node.js backend", "Python backend", "Go backend"), and technical synonyms ("SSE/WebSocket", "REST API with frontend") — comprehensive coverage including variations, matching anchor 5.

5 / 5

Distinctiveness Conflict Risk

The full-stack/backend niche with stack-specific triggers and negative triggers ("pure frontend UI work, pure CSS/styling, database schema only") is mostly distinct, but broad items like "implementing error handling" and "managing config/auth" could overlap with language-specific backend or auth skills — minor overlap risk, matching anchor 4 rather than anchor 5's minimal-conflict niche.

4 / 5

Total

18

/

20

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 (1052 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
UnicomAI/wanwu
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.