agentsclimarketplace

Build intuitive rca wiki

Skill cskwork/build-intuitive-rca-wiki

Turn technical incident RCAs into intuitive standalone HTML wikis for nondevelopers

Install
npx -y skills add cskwork/build-intuitive-rca-wiki

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Turn technical incidents, rollback reports, root-cause analyses, postmortems, and system failure explanations into intuitive standalone HTML wikis for nondevelopers. Use when a user asks for a visual or easy-to-understand incident explanation, a beginner-friendly RCA page, a reusable one-file HTML wiki, or when raw IDs, table names, error codes, and architecture diagrams need a plain-language presentation layer.

SKILL.md

3.7 KB, as published. Nobody here has run it

Build Intuitive RCA Wiki

Create one self-contained HTML file that a manager, operator, teacher, or other nondeveloper can understand in about three minutes. Preserve technical evidence, but place it behind plain-language conclusions.

Workflow

  1. Inspect the source material and separate evidence from inference.

  2. Replace system identifiers with audience-facing names in the main story.

  3. Build an input JSON file using references/content-contract.md.

  4. Keep raw IDs, table names, stack traces, SQL, and code paths only in technical_details.

  5. Generate the wiki:

    python3 scripts/render_wiki.py incident.json incident-wiki.html

  6. Validate the output:

    python3 scripts/validate_wiki.py incident-wiki.html

  7. Open the HTML in a real browser and inspect desktop and narrow mobile widths.

  8. Report which claims are confirmed, which remain pending, and which checks ran.

Use references/example-incident.json as a starting point when no structured input exists.

Content rules

  • Lead with one plain-language conclusion and one next action.
  • Tell the incident as 3–8 short numbered steps.
  • Use one familiar analogy when it materially reduces cognitive load.
  • Separate similar-looking failures, such as login failure versus a screen that fails after login.
  • Label evidence as confirmed or pending; never turn an inference into fact.
  • Give every raw value a human label. Prefer “current class” over 16002.
  • Put raw values in collapsed technical details, not headings or primary cards.
  • Define unavoidable jargon at first use.
  • Redact secrets, personal data, internal hostnames, tokens, and production-only identifiers unless the user explicitly authorizes their inclusion.
  • Preserve relative links only. Do not embed external fonts, scripts, trackers, or network dependencies.

Visual rules

  • Keep the page useful in one file and printable.
  • Make the reading order obvious: conclusion → flow → analogy/comparison → evidence → action → technical details.
  • Use color as reinforcement, never as the only status signal.
  • Maintain visible focus styles, semantic headings, keyboard-safe controls, and reduced-motion behavior.
  • Avoid dashboards, dense architecture canvases, tiny labels, raw-code walls, and decorative animation.
  • Prefer editorial spacing, large type, and short cards over compressed tables.

Quality gate

Do not finish until all of these are true:

  • The first screen answers “what happened?” without technical identifiers.
  • A nondeveloper can retell the sequence after reading the numbered flow.
  • Confirmed and pending claims are visibly distinct.
  • Technical detail is available but collapsed by default.
  • The generator and validator both pass.
  • Browser inspection covers desktop and mobile widths.
  • The output contains no secrets, external runtime dependencies, or absolute local file paths.

Resources

  • scripts/render_wiki.py: validate JSON and render escaped static HTML.
  • scripts/validate_wiki.py: check structure, privacy, links, and offline safety.
  • assets/wiki-template.html: dependency-free responsive presentation shell.
  • references/content-contract.md: input schema and writing guidance.
  • references/example-incident.json: generic example with no organization data.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.