CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

portfolio-pdlc-advance

Advance ONE initiative (or improvement bet) through the portfolio PDLC — do the stage-appropriate work that grows confidence, and prepare (never make) the human decision at the next boundary. Use when an item is aging, a discovery timebox lapsed without a recommendation, a decision is due or overdue, or a card is ready to move stage. The loop-1 skill of the portfolio-pdlc family.

Quality

94%

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

93%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 dense, actionable process skill: every section gives concrete moves, exact file and field names, and explicit decision gates, with depth correctly deferred to family skills. The single gap is the absence of error-recovery guidance when a quality gate fails.

DimensionReasoningScore

Conciseness

Lean throughout: the stage table compresses six stages of moves into six rows, and no line explains concepts Claude already knows — everything is operational ("Set the card's next_decision (date — decision — owner) and stop there"). The only near-duplicate, the confidence-not-cards motto, appears once as outcome framing and once as a rule, each earning its place.

5 / 5

Actionability

Fully concrete for an instruction-only skill: exact paths ("reviews/YYYY-MM-DD-<slug>-decision.md"), exact card fields ("stage", "stage_entered", "next_decision"), a fully specified brief structure, named compose tools ("intent-framing-chooser", "sniff-test"), and named options ("double down / de-risk further / kill-pause").

5 / 5

Workflow Clarity

The decision-boundary sequence is numbered with explicit gates ("Only when a dated human decision exists in the card's Decision log") and verification ("confirm the flow-log row appeared"), plus a Quality Gates checklist. It falls just short of the 5 anchor because no error-recovery path exists when a gate fails — e.g., what to do if the flow-log row does not appear.

4 / 5

Progressive Disclosure

Acts as a clear overview with one-level-deep, well-signaled references to depth elsewhere ("skills/sniff-test/references/ (this repo)", "Umbrella: portfolio-pdlc (leverage table, loop mechanics)") while keeping the compact stage expectations inline where they belong. No bundle files exist and no content is bloated enough to require extraction.

5 / 5

Total

19

/

20

Passed

Description

91%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: explicit what and when, multiple natural trigger phrases, and clear scoping (ONE card, prepare-never-decide). Its only softness is family-vocabulary overlap with sibling skills and stage actions that are named but not enumerated.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — "do the stage-appropriate work that grows confidence", "prepare (never make) the human decision at the next boundary" — but does not enumerate what the stage-appropriate work is, leaving minor coverage gaps. It goes beyond the 1-2 actions of the 3 anchor without the comprehensive action list of the 5 anchor.

4 / 5

Completeness

Explicitly answers both what ("Advance ONE initiative (or improvement bet) through the portfolio PDLC — do the stage-appropriate work that grows confidence, and prepare (never make) the human decision") and when ("Use when an item is aging... or a card is ready to move stage") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

The "Use when" clause gives four natural triggers — "an item is aging", "a discovery timebox lapsed without a recommendation", "a decision is due or overdue", "a card is ready to move stage" — plus object synonyms (initiative / improvement bet / item / card) and due/overdue variants. Coverage is comprehensive for this domain, which has no file extensions to name.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (single-card PDLC advancement with the "prepare, never make the decision" framing and explicit "loop-1 skill of the portfolio-pdlc family" positioning), but family siblings like the "portfolio-pdlc" umbrella share the same vocabulary (card, stage, decision), leaving minor overlap risk with closely related skills.

4 / 5

Total

18

/

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-advance/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.