CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nasa-pm-lessons

Surface a matched excerpt from Jerry Madden's NASA project-management aphorisms (LLIS #1956) at the moment it fits: incident root-cause sections; ticket refinement; plan drafting; status updates; escalation calls. Loads only one category at a time — never the full list, never more than three aphorisms per response. DO NOT use this for regulatory, legal, or prize-dispute decisions; route those to Legal/Compliance/DPO. Triggers: 'root cause', 'refine this ticket', 'draft a plan', 'status update', 'should I escalate', 'stakeholder comms'.

Quality

83%

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

71%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.

Well-structured skill with excellent progressive disclosure and a concrete, example-driven workflow. The main defects are redundancy — the over-citing and legal-routing rules are each restated three to four times — and a misplaced skill-auditor cargo command in the Verification section that reads as leftover tooling rather than skill guidance.

Suggestions

Remove the 'cargo run -p pantheon-skill-auditor ...' command and its JSON-grade explanation from the Verification section — it is skill-audit tooling, not guidance for applying the skill, and makes the verification step incoherent.

Consolidate the repeated over-citing and legal-routing guidance: it currently appears in When Not to Use, Verification, Mindset, and Anti-Patterns; state it once in Anti-Patterns (where it is already well-formed) and trim the rest.

Merge or shrink the overlapping Mindset and Anti-Patterns sections — three of the four Mindset bullets restate Anti-Pattern rules in softer form.

DimensionReasoningScore

Conciseness

Mostly efficient, but the same constraints (citation limits, routing regulated decisions) are repeated across When Not to Use, Verification, Mindset, and Anti-Patterns, and the 'cargo run -p pantheon-skill-auditor' command under Verification is skill-audit tooling irrelevant to applying the skill. More than minor trimming needed, so not a 4.

3 / 5

Actionability

Concrete, executable guidance: a scenario-to-file table, a four-step workflow, and a worked output example ('Working with Superiors — LLIS #1956: ... / Applied: ...') showing the exact citation format. Not a 5 because the misplaced auditor command and the exact placement rule for the attribution line leave minor gaps.

4 / 5

Workflow Clarity

The workflow is clearly sequenced (identify scenario → load matching file → pick 1-3 aphorisms → state, attribute, apply) with a no-fit fallback in Troubleshooting ('say so directly and skip the citation'). Not a 5 because the Verification section mixes a human-signoff checkpoint with the unrelated audit command and its sample output, blurring the sequence's validation step.

4 / 5

Progressive Disclosure

The body is a lean overview with two navigation tables (When to Use mapping scenarios to files, plus a References index), and all six references/*.md files exist exactly one level deep with no nested references — clear, well-signaled structure.

5 / 5

Total

16

/

20

Passed

Description

87%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.

Strong description: third-person voice, concrete what/when, natural trigger phrases, and explicit boundary routing. The only gap is that trigger coverage misses some synonym phrasings (postmortem, retro, 1:1) that the body's scenario table actually covers.

DimensionReasoningScore

Specificity

Concrete actions are named — 'Surface a matched excerpt', 'Loads only one category at a time — never the full list, never more than three aphorisms per response' — plus explicit out-of-scope routing. Not a 5 because the core capability is a single action (surface a matched excerpt) with constraints rather than a list of multiple distinct capabilities.

4 / 5

Completeness

Both what ('Surface a matched excerpt from Jerry Madden's NASA project-management aphorisms (LLIS #1956)') and when ('incident root-cause sections; ticket refinement; plan drafting; status updates; escalation calls' plus an explicit Triggers list) are clearly and explicitly answered with concrete trigger phrases, and out-of-scope cases are stated.

5 / 5

Trigger Term Quality

Natural trigger phrases users would actually say — 'root cause', 'refine this ticket', 'draft a plan', 'status update', 'should I escalate', 'stakeholder comms' — mapped to concrete scenarios. Not a 5 because common variations like 'postmortem', 'retro', 'incident writeup', or '1:1' are absent from the trigger list.

4 / 5

Distinctiveness Conflict Risk

A clear niche (NASA PM aphorisms, LLIS #1956) with distinct trigger phrases and explicit negative guidance ('DO NOT use this for regulatory, legal, or prize-dispute decisions') — minimal conflict risk with any other skill.

5 / 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

pantheon-org/tekhne

Path

skills/project-mgmt/nasa-pm-lessons/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.