CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

portfolio-pdlc-assess

The sensing pass of the portfolio-pdlc operating system. Use when asking "where is everything really, and is it outcome-oriented or activity-oriented?" — full portfolio reads, review/investment-council prep, stale-status sweeps, or restoring board integrity after contract violations. Verifies stages against evidence, classifies every card on the input→impact ladder, reads flow and risk balance, and outputs a review brief with ranked candidate moves. Composes the sniff-test and sniff-test-portfolio skills included in this repo.

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 well-crafted orchestration skill: tightly written, sequenced with explicit ordering and exit gates, and honest about coverage limits. The main gaps are the unnamed board-regeneration script in step 1, some redundant restatement of the sweep-first rule, and an inconsistent template path.

Suggestions

Name the board-regeneration script and its invocation in step 1 (e.g., `python scripts/regenerate_board.py`) so the workflow's entry point is executable rather than a placeholder.

State the stage-before-balance ordering once (the Rules bullet) and trim its repetition in workflow step 2 and Quality Gates to recover tokens.

Use one canonical path for the review template — `templates/review.md` in Modes and `skills/portfolio-pdlc/templates/review.md` in References appear to reference the same file inconsistently.

DimensionReasoningScore

Conciseness

Dense and procedural with almost no explanation of concepts Claude already knows, but the stage-before-balance ordering is stated three times (workflow step 2's "Do this before any balance or flow claim", the Rules bullet, and Quality Gates) and a few rhetorical asides ("a board that can't build lies about everything else") could be trimmed. Not 5 because of this repetition; well above 3 since every step still carries actionable specifics.

4 / 5

Actionability

Concrete guidance throughout — named evidence sources ("artifacts present, decision-log entries, shipped output, tracker/git history, dates"), named fields to write (`stage`/`stage_entered`, `orientation`), and a three-branch classification rule. Not 5 because step 1 says "Regenerate the board (script)" without naming the script or its command, leaving the entry-point action under-specified.

4 / 5

Workflow Clarity

Clear six-step sequence with enforced ordering ("Fix contract violations first", "Do this before any balance or flow claim"), an explicit exit checklist (Quality Gates: "zero contract violations at exit", "Every Tier-1 card has a current, cited orientation value"), and error handling (unreachable evidence gets "unverified", corrections logged in Evidence logs, board regenerated before and after). Not 4 because validation checkpoints are explicit, not merely implied.

5 / 5

Progressive Disclosure

Well-sectioned body with clearly signaled one-level-deep references (derisking rubric, council template) and the core rubric usefully inlined in step 4 with a pointer to the full reference. Not 5 because the skill ships no bundle files of its own and the template path is given inconsistently ("`templates/review.md`" in Modes vs "`skills/portfolio-pdlc/templates/review.md`" in References), a minor navigation gap.

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 third-person capability statements paired with an explicit, naturally phrased 'Use when' clause and a distinctive niche. The only weakness is that a few plausible synonyms for the trigger scenarios are absent.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Verifies stages against evidence", "classifies every card on the input→impact ladder", "reads flow and risk balance", "outputs a review brief with ranked candidate moves" — covering the skill's capabilities comprehensively with no vague padding.

5 / 5

Completeness

Explicitly answers both: what ("verifies stages… classifies every card… reads flow and risk balance… outputs a review brief with ranked candidate moves") and when ("Use when asking 'where is everything really, and is it outcome-oriented or activity-oriented?' — full portfolio reads, review/investment-council prep, stale-status sweeps, or restoring board integrity after contract violations") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-language triggers ("full portfolio reads", "review/investment-council prep", "stale-status sweeps", the quoted "where is everything really" question), but a few natural variations users might say (e.g., "portfolio audit", "board review", "status check") are missing. Not 5 because synonym coverage is not comprehensive; not 3 because the terms present are the phrases a practitioner would actually use.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche ("The sensing pass of the portfolio-pdlc operating system") with distinct triggers, and explicitly delimits its relationship to the composed skills ("Composes the sniff-test and sniff-test-portfolio skills"), minimizing wrong-skill triggering.

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