CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cs-backend-review

Backend engineering review — walks the 7 Matt Pocock forcing questions (read/write ratio + QPS, tenancy, sync vs async, data sensitivity, pattern, RPO/RTO, SLO), picks the language + pattern profile, forks into specialists (api-design-reviewer, database-designer, migration-architect, slo-architect). Invokes the cs-backend-engineer agent with context fork.

Quality

80%

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 ./.gemini/skills/cs-backend-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a lean, well-sequenced review protocol: a concrete CLI decision engine with full flag enumeration, explicit kill-criteria checkpoints, dependency-ordered specialist forks, and a bounded output digest. Remaining gaps are minor — no invocation syntax for the specialists, no specified recovery loop after a kill-criteria STOP, and references that point outside the skill bundle.

DimensionReasoningScore

Conciseness

Lean command-style body with zero padding: no explanation of concepts Claude already knows, every section (Routing protocol, Output expectations, Anti-patterns, Customization, Related commands) carries decision-relevant content. Not 4: there is no over-explanation left to trim — the only near-redundancy (the forcing_questions.md path appears twice) is navigationally useful, not padding.

5 / 5

Actionability

The fully-flagged `python engineering-team/skills/senior-backend/scripts/backend_decision_engine.py --team-size <N> --qps-p99 <N> ...` command is executable with all enum options spelled out, and kill criteria are concretely instantiated ('microservices, team size 5' trips Newman's MonolithFirst). Not 5: specialist forks are named and ordered but given no invocation syntax, and the tracking file `/tmp/backend-grill-<date>.md` has no specified format.

4 / 5

Workflow Clarity

The 5-step routing protocol is clearly sequenced with dependency ordering ('slo-architect FIRST — no SLO, no design', 'migration-architect — only if changing existing schema') and an explicit validation checkpoint (step 2 kill criteria: STOP and resolve), plus a ≤200-word output checklist. Not 5: the recovery path after a kill-criteria STOP is not spelled out — there is a stop but no explicit fix-and-retry loop.

4 / 5

Progressive Disclosure

The body acts as an overview with clearly signaled, one-level-deep pointers to detail ('Canonical source: .../references/forcing_questions.md', the decision-engine script, and the profiles/ directory for customization), and is well-sectioned. Not 5: no bundle files ship in this skill's directory (references/, scripts/, assets/ are absent), and the referenced paths live under an external engineering-team/ tree, so the referenced structure cannot be verified from the skill itself.

4 / 5

Total

17

/

20

Passed

Description

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

The description is highly specific and comprehensive, enumerating all seven forcing questions and the exact specialist agents involved, in clean third-person voice. Its main weakness is the absence of any explicit 'Use when...' trigger clause, which caps completeness at 3, alongside a few missing natural trigger phrases.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to review a backend service or design, validate scalability/tenancy/SLO decisions, or pick a language and architecture pattern.'

Include natural phrases users would actually say — 'backend design review', 'API design', 'database schema', 'service architecture' — to broaden trigger-term coverage.

Briefly state the expected output (matched profile, SLO targets, approver chain) so the 'what' also covers deliverables.

DimensionReasoningScore

Specificity

Enumerates all seven forcing questions by name ('read/write ratio + QPS', 'tenancy', 'sync vs async', 'data sensitivity', 'pattern', 'RPO/RTO', 'SLO') and multiple concrete actions ('picks the language + pattern profile', 'forks into specialists (api-design-reviewer, database-designer, migration-architect, slo-architect)', 'Invokes the cs-backend-engineer agent with context fork') — comprehensive coverage of what the skill does, all in third person. Not 4: there are no coverage gaps in the action list; the seven questions and fork targets are each named explicitly.

5 / 5

Completeness

Has a clear 'what' (walks the 7 forcing questions, picks the profile, forks into specialists) but no 'Use when...' clause or equivalent explicit trigger guidance; when to use it is only weakly implied by the 'Backend engineering review' domain label. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural domain keywords ('Backend engineering review', 'read/write ratio + QPS', 'tenancy', 'sync vs async', 'RPO/RTO', 'SLO') that a user needing this skill would plausibly say. Not 5: common variations like 'API design', 'database schema', 'service architecture', or 'scalability review' are missing. Not 3: coverage goes well beyond a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

'Backend engineering review' plus named specialists (slo-architect, migration-architect, etc.) carves a mostly distinct niche with clear triggers. Not 5: it sits inside a family of closely related commands (/cs-fullstack-review, /cs-frontend-review) and a generic 'review my service' request could overlap with those.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/cs-backend-review/SKILL.md

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.