FreeWebVerifiedProject Knowledge Graph Web Page
v1.0.9Use it to build a web page.
Run in your terminal (sign in once with npx skillloom-cli login):
npx skillloom-cli install sl-project-knowledge-graph-web-pageUpdated Oct 5, 2026
- Install guides
- Claude CodeCodex
- Generates with
- Host Agent LLM
- In the package
6 files · 19.4 KB
- SKILL.md
- references/framework-adaptation.md
- references/section-library.md
- references/style-guide.md
- references/template.html
- scripts/validate-html.mjs
Similar skills
FreeWebVerified
WebVerifiedSpreadsheet Data Grid UI Block
Works with: Claude Code, Cursor, OpenCode, Codex, Gemini CLI
WebVerifiedEvent Bar Chart UI Block
Works with: Claude Code, Cursor, OpenCode, Codex, Gemini CLI
WebVerifiedOrbit Admin Dashboard UI Block
Works with: Claude Code, Cursor, OpenCode, Codex, Gemini CLI
WebVerifiedRecords Data Grid UI Block
Works with: Claude Code, Cursor, OpenCode, Codex, Gemini CLI
WebVerifiedPaired Column Chart UI Block
Works with: Claude Code, Cursor, OpenCode, Codex, Gemini CLI
WebVerifiedDark Balance Chart UI Block
Works with: Claude Code, Cursor, OpenCode, Codex, Gemini CLI
FreeWebVerifiedActivity Calendar Chart UI Block
Works with: Claude Code, Cursor, OpenCode, Codex, Gemini CLIWhat you get
- A central project thesis with connected evidence clusters and dependency paths.
- Citation-led claim cards with source, date, owner, and confidence context.
- Responsive relationship blocks for milestones, risks, decisions, and technical entities.
- Executive summary language that preserves the distinction between fact, inference, and open question.
- A self-contained page structure that can be ported to React, Vue, or utility CSS.
Good fit
- Client or executive reporting where decisions need traceable evidence.
- Research and technical communication with many linked sources and dependencies.
- Project status pages that must expose assumptions, risks, and lineage clearly.
Not for
- Unverified content with no source inventory or evidence trail.
- Brand-led campaign pages focused on visual emotion instead of project reasoning.
- Private graph exploration tools requiring authentication, editing, or live collaboration.
Try this prompt
You say
/sl-project-knowledge-graph-web-page Create an Axiom Atlas page for executives exploring HelioGrid evidence: navigation, split hero, six-source register, four evidence features, a thesis, four program stats, four source-to-decision steps, four evidence clusters, three open questions, CTA, and footer, in that order. Use headline “Every decision has a trace.” and closing CTA “Make the evidence legible.” Style: dark canvas, mint facts, blue relationship lines, [S1]-[S6] claim markers.

Then try
Add a technical lineage section showing how ingestion, validation, modeling, and reporting depend on one another.
Rewrite the evidence clusters for a board audience while keeping every source key and uncertainty label intact.
Create a mobile-first version where the graph becomes a numbered evidence trail with expandable source details.
What you provide
- A project question or executive decision context.
- A source list with claims, quotations, dates, and provenance.
- The key entities, dependencies, milestones, risks, and unresolved questions.
- The intended audience and any terminology or confidentiality requirements.
Requirements
- A modern browser
- Node.js 20+ for the validator
Running cost
No external services. Runs entirely on your agent.
Verification
4.0/ 5
Render score
Verified
| Real render check | Verified | 4.0 / 5 | 12s |
|---|
FAQ
Can the page show uncertainty instead of presenting every claim as fact?
Yes. The structure supports confidence labels, unresolved question blocks, and explicit distinctions between sourced facts, analyst interpretation, and pending validation.
What makes this different from a generic project dashboard?
The page is organized around relationships and provenance. Each important statement has a visible route to its source, while dependencies and decisions explain why the information matters.
Can a large source set be summarized for executives?
Yes. Lead with a concise thesis and implications, then expose selected evidence clusters and source keys so readers can move from decision context to technical detail.