CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

principle-redesign-from-first-principles

Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.

55

Quality

69%

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 ./plugins/pstack/skills/principle-redesign-from-first-principles/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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, principle-driven skill that assumes Claude's competence and avoids padding entirely. Its weaknesses are that the guidance stays directional rather than demonstrable — no example of a propagated redesign — and the workflow is only implicitly sequenced with no verification checkpoint.

Suggestions

Add one short before/after example showing a requirement bolted on vs. redesigned from first principles, to make the propagation bullet concrete and executable.

Number the bullets into an explicit sequence (read, ask, propagate, deliver) and add a final verification step such as 'confirm no reference still reflects the old design' so the workflow has a checkpoint.

Collapse the opening paragraph's three restatements of the same idea into one sentence to reclaim tokens.

DimensionReasoningScore

Conciseness

The body is lean with no concept re-teaching, but the opening paragraph restates the same idea three times ('don't bolt it onto the existing design' / 'Redesign as if the requirement had been there from the start' / 'what we would have built if we'd known on day one'), which is minor over-explanation that could be trimmed.

4 / 5

Actionability

The bullets give real direction ('Read all affected files', 'Propagate the change through every reference: types, docs, examples, rationale sections'), but there is no worked example or concrete checklist of what propagation looks like, and 'Think about the redesign holistically, then deliver it incrementally' is abstract — 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The bullets imply a rough order (read, ask, propagate, deliver) but are not explicitly sequenced, and the closing guidance leaves the delivery order and any verification checkpoints implicit, fitting 'steps listed but sequence present with checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

This is a single-purpose skill under 50 lines with no need for external references; the heading, intro, bullet list, and closing line are well organized, which per the rubric's simple-skill guidance earns the top score without external file references.

5 / 5

Total

15

/

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.

The description cleanly states both what the skill does and when to apply it, with a memorable framing ('instead of bolting it on'). However, it names only one action, provides a single trigger phrase without synonyms, and its broad integration trigger risks overlap with general refactoring skills.

Suggestions

Add 1-2 more concrete capability statements, e.g. 'Propagate the change through types, docs, examples, and rationale sections' so the description lists multiple specific actions.

Broaden trigger coverage with natural variations users would say, such as 'add a feature to an existing design', 'refactor to incorporate a new requirement', or 'update the design holistically'.

Sharpen the distinctiveness of the trigger by scoping it, e.g. 'when a new requirement changes an established design's structure or assumptions' rather than any change integration.

DimensionReasoningScore

Specificity

Names the domain ('integrating a new requirement into an existing design') and one concrete action ('Redesign as if the requirement had been a foundational assumption from day one'), but does not enumerate multiple specific capabilities, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Explicitly answers both 'what' (redesign as if the requirement had been foundational) and 'when' ('Apply when integrating a new requirement into an existing design'), but offers only a single trigger phrase rather than the multiple concrete triggers of the top anchor.

4 / 5

Trigger Term Quality

Contains relevant phrases like 'integrating a new requirement' and 'bolting it on', but misses common variations users would naturally say such as 'add a feature', 'refactor the design', or 'propagate a change', fitting the 'some relevant keywords but missing synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

The trigger 'integrating a new requirement into an existing design' is fairly broad and overlaps with general feature-addition and refactoring skills, so it is 'somewhat specific but could still overlap with similar skills'.

3 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

adamsardo/pstack-claude

Path

plugins/pstack/skills/principle-redesign-from-first-principles/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.