pdlc-harness-readiness
White-box assessment of a spec-driven harness or coding-agent configuration from a public GitHub repository, local directory, ZIP archive, or effective instruction hierarchy. Use when a CTO, VPE, or AI adoption leader wants evidence-backed feedback on outcome discovery, trustworthy delivery, in-use validation, and how the harness improves its own loop. For a produced spec as black-box evidence, use pdlc-readiness instead.
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required workflow ingests external public GitHub repositories and ZIP archives containing outsider-authored code and instruction files.
- Repository
yyeret/portfolio-pdlc
- Revision
cb337f8
- Audited
- Security analysis
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.