CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pdlc-readiness

Assess a produced spec or spec bundle as black-box evidence of outcome orientation and PDLC readiness. Use when a CTO, VPE, or AI adoption leader wants to improve a spec-driven harness from its outputs, separating current-spec repairs from reusable workflow changes. For white-box inspection of a harness repository or agent configuration, use pdlc-harness-readiness.

Quality

86%

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

85%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-structured assessment skill: the body stays a lean overview, delegates detail to real, clearly-signaled one-level-deep reference files, and provides a sequenced workflow with explicit validation and fallback behavior. The only notable improvements are tightening a few over-stacked sentences and adding a brief worked example of a rated output.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and assumes Claude's competence without explaining known concepts; only minor trimming is possible (e.g., the stacked clauses in step 8's Jev instructions and several multi-clause sentences), keeping it just below the 'every token earns its place' anchor.

4 / 5

Actionability

Concrete, executable guidance throughout for an instruction-only skill: eight ordered assessment steps name exactly what to look for ('what authorizes commitment, what done or archive means'), six named yield controls with 0-2 anchors, a concrete deliverable pair, and an example filename ('reviews/2026-10-05-checkout-pdlc-readiness.{md,html}'). The minor gap is the absence of a worked example of a rated assessment inline.

4 / 5

Workflow Clarity

A clear Intake -> Assessment (8 ordered steps) -> Deliverable -> Validation sequence is present with explicit validation checkpoints ('check the brief against references/tests.md', 'Verify citations and consistency across the two views') and error-recovery feedback loops ('If Jev is unavailable, complete the assessment without it and state that no classifier run occurred'; 'If file creation is unavailable, provide the same brief in chat').

5 / 5

Progressive Disclosure

SKILL.md is a ~72-line overview that clearly signals one-level-deep references, each at the relevant section with its purpose stated ('Read references/rubric.md for the dimensions, indicator test, rating anchors, and verdict rules'); all six bundle files (rubric.md, comparisons.md, jev-classifiers.md, report-contract.md, tests.md, assets/report.html) exist and no reference nests further references.

5 / 5

Total

18

/

20

Passed

Description

82%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 with an explicit 'Use when...' clause, concrete audience triggers, and clear boundary routing to the sibling white-box skill. Its main weakness is that the stated actions are somewhat abstract, and a few natural synonyms (specification, requirements) would broaden triggering.

Suggestions

Add one or two plain-language synonyms (e.g., 'specification' or 'requirements document') to the trigger phrasing so users who don't say 'spec' still match.

Ground the 'what' with one more concrete output-side action (e.g., 'rate seven evidence dimensions and produce a Markdown brief plus HTML report') to lift specificity beyond abstract judgment language.

DimensionReasoningScore

Specificity

The description names the domain ('produced spec or spec bundle', 'PDLC readiness') and 1-2 concrete actions ('assess... as black-box evidence', 'separating current-spec repairs from reusable workflow changes'), but the actions are abstract judgments rather than the several concrete operations of the higher anchors.

3 / 5

Completeness

It explicitly answers both what ('Assess a produced spec or spec bundle as black-box evidence of outcome orientation and PDLC readiness') and when ('Use when a CTO, VPE, or AI adoption leader wants to improve a spec-driven harness from its outputs'), with concrete trigger phrasing and explicit routing to the sibling skill for the white-box case.

5 / 5

Trigger Term Quality

Natural terms like 'spec', 'spec bundle', 'spec-driven harness', and 'PDLC readiness' appear alongside a role-based trigger ('Use when a CTO, VPE, or AI adoption leader wants to improve a spec-driven harness from its outputs'), but common synonyms such as 'specification' or 'requirements' are missing.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (black-box assessment of produced specs) and explicitly disambiguates from the closely related skill ('For white-box inspection of a harness repository or agent configuration, use pdlc-harness-readiness'), minimizing wrong-skill triggering.

5 / 5

Total

17

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

yyeret/portfolio-pdlc

Path

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