CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cs-fullstack-review

Fullstack engineering review — walks the 7 Matt Pocock forcing questions, picks the profile, forks into POWERFUL specialists (api-design-reviewer, database-designer, slo-architect). Invokes the cs-fullstack-engineer agent with context fork.

Quality

75%

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-fullstack-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.

A tight, well-structured router skill: token-efficient, sequenced with genuine checkpoints, and concrete enough to act on, with detail properly pushed to reference files. The main gaps are unenumerated CLI argument values, no error/loop-back path for the decision engine, and references that point outside the bundle rather than to shipped files.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout — terse 7-item question list, numbered routing steps, bulleted output expectations and anti-patterns — with zero explanation of concepts Claude already knows (no primer on microservices, p99, or CI/CD). Fits anchor 5: every token earns its place and Claude's competence is assumed.

5 / 5

Actionability

The routing protocol gives a concrete, copy-paste-shaped command (`python engineering-team/skills/senior-fullstack/scripts/fullstack_decision_engine.py --team-size <N> ... --budget <USD/mo>`) plus a concrete tracking path (`/tmp/fullstack-grill-<date>.md`). Not 5: valid values for `--cadence`, `--data-sensitivity <tier>`, and `--user-facing` are never enumerated, and the referenced script is not present in the bundle, so the command cannot actually be executed as written. Not 3: the guidance is genuinely concrete, not pseudocode or high-level hints.

4 / 5

Workflow Clarity

Clear 5-step sequence (walk questions → kill-criteria check → decision engine → profile + runner-up → fork specialists) with real checkpoints: "if any question trips one (e.g., 'microservices day 1, team size 3'), STOP and resolve before proceeding" and the 15% runner-up tradeoff rule. Not 5: the kill criteria themselves are only exemplified, not enumerated, there is no loop-back if the decision engine fails or yields no match, and nothing validates the final digest against the ≤200-word expectation.

4 / 5

Progressive Disclosure

Good structure with clearly signaled, one-level-deep references — "Canonical source: engineering-team/skills/senior-fullstack/references/forcing_questions.md" — and detail correctly delegated out of the overview (canon citations, profile JSONs, decision logic). Not 5: the referenced files (forcing_questions.md, fullstack_decision_engine.py, profiles/) do not exist in this bundle — no references/, scripts/, or assets/ directories are present — so navigation cannot be verified and the paths read as raw repo paths rather than in-bundle links.

4 / 5

Total

17

/

20

Passed

Description

58%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 reasonably specific, third-person description with a clear "what" and a distinct fullstack niche, but it is missing any "when to use" trigger guidance and leans on internal jargon (forcing questions, context fork, agent names) rather than natural user vocabulary. Completeness is capped at 3 by the absent Use-when clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for a fullstack/architecture review of an app or codebase, is choosing a tech stack, or mentions fullstack, frontend-plus-backend, or stack decisions."

Include natural synonyms users would actually say — "tech stack review", "architecture review", "stack selection", "web app review" — alongside the domain jargon.

State the deliverable (a ≤200-word digest with matched profile, success criteria, and approver chain) so the "what" covers the outcome, not just the process.

DimensionReasoningScore

Specificity

Lists several concrete actions — "walks the 7 Matt Pocock forcing questions, picks the profile, forks into POWERFUL specialists (api-design-reviewer, database-designer, slo-architect). Invokes the cs-fullstack-engineer agent" — with named specialists beyond the 1-2 actions of anchor 3. Not 5: it never states what the review actually delivers (output/deliverable), so coverage has minor gaps.

4 / 5

Completeness

The "what" is clear (walks forcing questions, picks profile, forks to specialists), but there is no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. Not 2: the "what" is concrete, not vague; not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"Fullstack engineering review" is a relevant natural phrase, but the rest is internal jargon users would not say ("Matt Pocock forcing questions", "context fork", agent names like "slo-architect"), and common variations such as "tech stack", "architecture review", "stack choice", or "code review" are absent. Not 4: keyword coverage is thin — a user asking for a stack or architecture review would not naturally match these terms.

3 / 5

Distinctiveness Conflict Risk

The "fullstack" scope plus named agents (cs-fullstack-engineer, api-design-reviewer) carve a clear niche, but sibling commands in the same family (/cs-frontend-review, /cs-backend-review, /cs-engineer-grill) overlap and the description offers no trigger to choose between them. Fits anchor 4 (mostly distinct, minor overlap with closely related skills); not 5 because that family overlap is unaddressed.

4 / 5

Total

14

/

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-fullstack-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.