CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gstack-plan

Use before building a feature: challenge the scope, then review architecture, code quality, tests and performance, and end with a plan to build. (gstack)

Quality

79%

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 ./qm/sandbox/skills/gstack-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tightly written, instruction-only review workflow: every section prescribes concrete actions with thresholds, stop-and-ask checkpoints, and a specified final deliverable. It stays below top marks only for minor trims, a missing output template and loop-back step, and a monolithic single-file structure that is defensible but not optimally split.

Suggestions

Add an explicit loop-back step after the user answers scope questions (e.g., re-run the complexity count on the agreed scope before starting Section 1) to close the feedback loop.

Specify the output format for findings, e.g., a one-line example of 'severity, recommendation, alternative' as recorded in the plan.

Consider moving the eight red flags and design-twice detail into a references/ file loaded only when the plan introduces a new module or boundary, keeping SKILL.md as the overview.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive ('require common behavior and improved reliability or net savings; similar-looking code alone is insufficient', 'At 8+ files or 2+ new classes or services, propose a smaller arrangement') with no explanations of concepts Claude already knows. Minor over-explanation in the design-twice prose ('A plan with one design usually took the first shape that compiled in the author's head') keeps it below the lean-every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete commands ('git log --oneline -10', 'ls'), explicit thresholds ('At 8+ files or 2+ new classes or services'), and specific instructions ('sketch one in five lines (types and signatures, bodies `not implemented`)', 'Give each finding's scale (rows, requests/s, bytes) or mark it unknown; never invent benchmarks') make the guidance mostly executable. Minor gaps: no example finding or revised-plan template, and 'run with `execute`' is ambiguous outside its host harness.

4 / 5

Workflow Clarity

The sequence is explicit ('Work through Scope Challenge, then Sections 1-4 in order') with real checkpoints ('Complete these checks before proposing scope changes', 'Ask about decisions that change scope in one message and stop until the user answers') and a conditional rule for the design-twice sub-procedure. Not a 5: there is no loop-back step after the user answers scope questions and no final verification that the revised plan resolves the recorded findings.

4 / 5

Progressive Disclosure

Sections are well organized (Assess the target, Sections 1-4, design-twice) and a single self-contained file is appropriate since all sections are used every run ('Never condense, abbreviate or skip a section'); no bundle files exist to reference. Not a 5: at ~125 lines, the ~40-line design-twice/red-flags block is a plausible candidate for a clearly signaled one-level-deep reference.

4 / 5

Total

16

/

20

Passed

Description

75%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 solid description that answers both what and when with several concrete actions and a distinctive plan-review framing. It falls short of top marks on missing synonyms for planning artifacts, an unstated review target, and modest overlap risk with general code-review skills.

Suggestions

State the review target explicitly, e.g., 'reviews a written plan or feature description, not code'.

Broaden trigger coverage with natural synonyms: 'Use before building a feature or when the user shares a plan, spec, or design to review'.

Replace the opaque '(gstack)' suffix with a clearer namespace cue or drop it, since users would not type it.

DimensionReasoningScore

Specificity

It lists several concrete actions — 'challenge the scope, then review architecture, code quality, tests and performance, and end with a plan to build' — matching the several-specific-actions anchor. Not a 5: the reviewed artifact (a plan vs. code) is never stated, and the actions are workflow-level rather than fully concrete.

4 / 5

Completeness

Both parts are present: the 'what' is 'challenge the scope, then review architecture, code quality, tests and performance, and end with a plan to build', and the 'when' is explicit via 'Use before building a feature'. Not a 5: the when-clause is a single brief condition without concrete trigger phrases; not a 3 because explicit 'Use before...' trigger guidance exists.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'building a feature', 'scope', 'architecture', 'code quality', 'tests', 'performance', 'plan' — terms a user planning a feature would plausibly say. Not a 5: common variations and synonyms like 'spec', 'design review', 'RFC', or 'tech plan' are missing; not a 3 because the coverage goes well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

The niche — scope challenge plus a fixed four-section engineering review ending in a revised plan, tagged '(gstack)' — is mostly distinct. Minor overlap risk: 'review architecture, code quality, tests and performance' could attract generic code-review requests even though the body reviews plans, not code.

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

garrytan/gstack

Path

qm/sandbox/skills/gstack-plan/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.