CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

portfolio-pdlc-strengthen

Improve the quality, outcome orientation, and derisking of ONE initiative's artifacts in the portfolio PDLC — rewrite activity-framed cards into outcome hypotheses with leading indicators, sharpen riskiest assumptions with evidence/opinion tags, fix derisking-approach mismatches, and capture at most one durable learning. Use on cards flagged activity-oriented, thin on evidence, missing indicators, or carrying committed money with open risks. The loop-2 skill of the portfolio-pdlc family.

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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, actionable editorial workflow with an explicit quality-gate checklist and clear boundaries on what the skill must not do (scope changes, orientation courtesy upgrades). The main gaps are executable detail delegated to family context (the learnings contract format, board regeneration) and a few terms defined nowhere within reach of this file.

Suggestions

Show or link the learnings 'contract format' — a compact template or a pointer to the family file that defines it — so step 7 is executable without external context.

Trim the Rules lines that restate the workflow verbatim ('Indicators without current values are flagged n/a, not invented'; 'One card, at most one learning, board regenerated') and keep only the constraints that add new information.

Give 'watermelon risk' and 'seek-alpha' a five-word gloss or fold them into the derisking-and-indicators reference so every term used is reachable from this file.

DimensionReasoningScore

Conciseness

The body is lean and compressed — no explanations of concepts Claude already knows, and jargon like 'Goldilocks' and 'OMTM' is used without padding. However, the Rules section restates workflow content ('Indicators without current values are flagged n/a, not invented' repeats step 3; 'One card, at most one learning, board regenerated' repeats steps 6–7), so it sits at 'efficient; minor instances that could be trimmed' rather than every token earning its place.

4 / 5

Actionability

Highly concrete for a judgment-based skill: a fill-in hypothesis template ('if [user/stakeholder] attains [benefit] via [change], we expect [business impact]'), an explicit risk-matching rule (low → just-do-it; medium → ship & measure; high → discovery/testing), named fields ('outcome_hypothesis', 'risk_level', 'derisking_approach'), and a concrete bad example ('12 features shipped'). Not 5 because 'contract format' for learnings and 'board regenerated' are invoked without a template or pointer, leaving steps 6–7 not fully executable from this file alone.

4 / 5

Workflow Clarity

Seven clearly sequenced steps (read cold → rewrite → indicators → assumptions → derisking fit → record → capture) close with an explicit Quality Gates checklist, and failure paths are handled ('or the brief says why not, and what's missing'; mismatch 'escalated as a candidate move'). This matches the anchor of a clear sequence with explicit validation steps and a checklist, and the single-card scope means no batch/destructive validation cap applies.

5 / 5

Progressive Disclosure

Good structure with well-organized sections and a single clearly signaled one-level-deep reference ('Ladder + Goldilocks/OMTM: skills/sniff-test/references/derisking-and-indicators.md (this repo)'). Docked from 5 because that path lives outside the skill's own bundle (no references/ directory ships with it) and in-body terms ('watermelon risk', 'seek-alpha', 'contract format') have no navigable definition — minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

92%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 strong description: concrete enumerated actions, an explicit 'Use on...' trigger clause with concrete flag conditions, and clear family positioning. The only shortfall is trigger synonym coverage, which is good but not exhaustive.

DimensionReasoningScore

Specificity

Lists four concrete actions — 'rewrite activity-framed cards into outcome hypotheses with leading indicators, sharpen riskiest assumptions with evidence/opinion tags, fix derisking-approach mismatches, and capture at most one durable learning' — which comprehensively cover the body's workflow. Matches the multiple-specific-actions/comprehensive-coverage anchor; the abstract lead-in ('Improve the quality, outcome orientation, and derisking') is immediately made concrete.

5 / 5

Completeness

Both halves are explicit: what = the four enumerated rewriting/sharpening/capture actions; when = 'Use on cards flagged activity-oriented, thin on evidence, missing indicators, or carrying committed money with open risks.' Concrete trigger phrases are present, matching the clearly-and-explicitly-both anchor.

5 / 5

Trigger Term Quality

'Use on cards flagged activity-oriented, thin on evidence, missing indicators, or carrying committed money with open risks' provides natural trigger phrases a user of this system would actually say. Falls just short of comprehensive: common variations such as 'outcome-oriented', 'OKR', 'hypothesis', or 'steering' are absent — good keyword coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

'The loop-2 skill of the portfolio-pdlc family' positions it within its family, and the narrow, flag-based triggers ('carrying committed money with open risks', 'missing indicators') carve a clear niche with minimal conflict risk — they would not naturally fire for sibling skills or generic planning skills. Not 4 because the overlap with closely related family skills is explicitly resolved by the loop-number positioning.

5 / 5

Total

19

/

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

yyeret/portfolio-pdlc

Path

skills/portfolio-pdlc-strengthen/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.