drawing UI consistently with agents, at the top of Design System + Component Library
SaferSkills independently audited pastiche (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Orchestrates pastiche-implementer-round1, pastiche-reviewer, and pastiche-implementer-round2 in a bounded loop, then emits a single task report.
Run ls pastiche/FACT.md pastiche/KNOWLEDGE.md pastiche/WISDOM.md. If any are missing, stop and report:
This project does not appear to have pastiche set up — expectedpastiche/{FACT,KNOWLEDGE,WISDOM}.md. Run/pastiche-initto scaffold them.
pastiche-implementer-round1 with {task} → capture {r1_report}.pastiche-reviewer with {task, r1_report} → capture {doubts}. The reply is either one or more lines of <path>#<line> | <comment>, or the literal (no doubts). If any line fails to match the record shape and the output isn't (no doubts), stop and report:Reviewer returned malformed output; expected<path>#<line> | <comment>records or the literal(no doubts).
{doubts} is (no doubts), go to 6 (no {r2_report}).pastiche-implementer-round2 with {task, r1_report, doubts} → capture {r2_report}.{r2_report}'s unresolved: block (skip if unresolved: -): Read the file, then Edit to insert a comment in the file's native comment syntax above the targeted <line> (matching surrounding indentation). Comment text: pastiche-unresolved-doubt: <comment from the unresolved: record>.build_command from pastiche/config.yaml. If null or absent, skip. Otherwise run it. For each error, patch using the build output as source of truth. Bounded to 3 patch attempts per error. If an error persists after 3 attempts, leave it and note it in Follow-ups.## Summary
- **Files changed:** <paths> (omit if none)
- **Implementation:** <2–3 sentences describing the end result>
## Follow-ups
- <location> — <one-line description>
- ... (omit section if no follow-ups)Files changed is the union of files: entries from {r1_report} and {r2_report}; omit the line if both are -.
Follow-up sources (each follow-up bullet must be self-describing; readers shouldn't need to know about rounds, dispositions, or the loop):
{r1_report}'s gaps: line → KNOWLEDGE.md — <scenario>.(knowledge-gap)-tagged record in {r2_report}'s defended: block → KNOWLEDGE.md — <reason>.(wisdom-gap)-tagged record in {r2_report}'s defended: block → WISDOM.md — <reason>.{r2_report}'s unresolved: block → <path>#<line> — <comment>.<path>:<line> — <comment>.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.