AB senior-backend
Production-grade backend development. Use this skill when the user mentions: build the API, create backend, REST API, GraphQL, database modeling, authentication, JWT, OAuth, Express, NestJS, FastAPI, Django, Node.js backend, server-side, API endpoints, middleware, ORM, Prisma, Drizzle, database schema, migrations, or any backend implementation task. Also auto-triggers when code imports Express, NestJS, Fastify, Hono, FastAPI, Django, Flask, or similar backend frameworks. Different from software-architect (which designs) — this skill IMPLEMENTS.
As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, consistency
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 66/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (senior-backend) differs from the folder (eb-senior-backend)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 18 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1488 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 550: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 18 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.