← ClaudeAtlas

hoo-import-auditlisted

Use to import an external claude-seo audit report or action plan as gated proposals - "import this audit", "turn this audit report into proposals", /organic-os:import-audit. They audit, we operate.
shalintripathi/organic-os · ★ 3 · AI & Automation · score 69
Install: claude install-skill shalintripathi/organic-os
# Import an external audit (claude-seo shape) Turns a point-in-time audit report into organic-os proposals without re-deriving the audit. The import trusts but attributes: findings keep their original evidence labels ([Measured]/[Inference]/[Unverified]), the original finding text rides in each proposal verbatim, and anything our own audit dimensions would dispute is flagged for the human, never silently rewritten. 1. Input: a file path from the user (a FULL-AUDIT-REPORT.md, an ACTION-PLAN.md, or similar markdown) or report text pasted in chat. Pasted text: write it to a temp file first. Read site-profile.yaml for the approval channel and the site URL. 2. Parse and rank with the import module - stdlib only, defensive by design (the format is theirs and may vary between versions; whatever matches no item pattern is preserved in `parsed["unparsed"]`, never dropped): `PYTHONPATH="$CLAUDE_PLUGIN_ROOT/lib" python3 -c` snippet importing `hoo.audit_import` - `parsed = parse_report(text)`, then `props = to_proposals(parsed, max_items=5)`. 3. Create each proposal via `create_item(kind=p["kind"], slug=p["slug"], title=p["title"], body=p["body"], target=<the finding's page URL if one appears in it, else parsed["source_meta"]["page_url"], else the profile site URL>, source="import-audit")`. `create_item` is the ONLY birth path - items are born `proposed` with an empty approvals list and are NEVER auto-approved; approval is the human's act, on the