Where
agent-pmo-skill/templates/skills/website-audit/SKILL.md (Step 11 — Audit Design Compliance), currently line ~131:
Read the design system docs and view the design screens in the designsystem folder.
Problem
This line is unconditional — it tells the agent to read a designsystem/ folder that most consuming repos do not have. When the skill runs in a repo without one (e.g. Basilisk), the agent wastes a step looking for a folder that isn't there and has to caveat the audit report ("the designsystem folder doesn't exist").
The neighbouring business-plan step already uses the correct conditional phrasing ("If the repo has a business plan doc, take it into account"). Step 11 should match.
Note: in at least one rendered/consumed copy, the business-plan step also showed up as a hard-coded broken markdown link — [text](../../../business_plan/business_plan.md) — pointing at a path that doesn't exist in the consuming repo. Worth confirming the renderer never emits dead relative links for optional resources.
Suggested fix
Make Step 11 conditional, e.g.:
If the repo has a design system (design tokens, component docs, or design screens), review it and check the site for compliance. Otherwise, audit the live site's visual consistency directly (spacing, type scale, color usage, component reuse).
Impact
Low severity, but it makes every website-audit run in a design-system-less repo emit a spurious "missing folder" caveat. Filed from the Basilisk repo where the rendered skill carried both the dead business_plan link and the unconditional designsystem reference.
Where
agent-pmo-skill/templates/skills/website-audit/SKILL.md(Step 11 — Audit Design Compliance), currently line ~131:Problem
This line is unconditional — it tells the agent to read a
designsystem/folder that most consuming repos do not have. When the skill runs in a repo without one (e.g.Basilisk), the agent wastes a step looking for a folder that isn't there and has to caveat the audit report ("the designsystem folder doesn't exist").The neighbouring business-plan step already uses the correct conditional phrasing ("If the repo has a business plan doc, take it into account"). Step 11 should match.
Note: in at least one rendered/consumed copy, the business-plan step also showed up as a hard-coded broken markdown link —
[text](../../../business_plan/business_plan.md)— pointing at a path that doesn't exist in the consuming repo. Worth confirming the renderer never emits dead relative links for optional resources.Suggested fix
Make Step 11 conditional, e.g.:
Impact
Low severity, but it makes every website-audit run in a design-system-less repo emit a spurious "missing folder" caveat. Filed from the Basilisk repo where the rendered skill carried both the dead
business_planlink and the unconditionaldesignsystemreference.