Renders project data into readable browser artifacts like quests, handoffs, or documents.
Install
mkdir -p .claude/skills/view-egregore-labs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17488" && unzip -o skill.zip -d .claude/skills/view-egregore-labs && rm skill.zipInstalls to .claude/skills/view-egregore-labs
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Fallback Codex adapter for the Egregore view workflow.Key capabilities
- →Resolve file or live Egregore surface
- →Render artifacts using in-repo tooling
- →Open rendered artifacts in a browser
- →Compose multi-section documents
- →Publish stable boards in connected mode
How it works
The skill resolves the requested artifact, selects the appropriate in-repo renderer, generates an HTML file, and opens it in the user's browser.
Inputs & outputs
When to use view
- →View a quest
- →Open project docs
- →Render network state
About this skill
Egregore View
Native Codex Egregore skill. Use only inside an Egregore checkout.
Resolve a file or live Egregore surface, render it with the in-repo artifact tooling, open it, and report the concrete output path. Run the workflow inline; do not invoke Claude Code commands or delegate through Loom.
Structured UX parity
The visible result is the browser artifact and a compact receipt. Preserve the typed artifact templates, designed document composition, exact file path, and stable board URL when available. Do not replace the artifact with a prose summary or expose raw renderer output.
Resolve the request
- Verify
bin/agent.shexists. If not, say this is not an Egregore checkout. - Parse an optional type followed by a name:
questfrommemory/quests/handofffrommemory/handoffs/recursivelyactivity,board, ornetworkwith no source filedocumentfor any markdown file
- Treat an argument containing
/or ending in.mdas a direct path. Use it if it exists and infer the type from its directory. - With no explicit type, search in this order: quests, handoffs, knowledge. Prefer exact basename matches, then case-insensitive partial matches. For handoffs, prefer the newest matching dated path.
- If several files match, use structured Codex question tooling when available; otherwise ask one concise plain-text question listing the paths.
- If no file matches and the input is a topic or question, synthesize a
temporary markdown document from relevant memory, repository files, and
conversation context at
/tmp/egregore-artifacts/synthesized-<slug>.md. If the input clearly names a missing file, report it as missing instead of inventing a document.
Select the renderer
Prefer the checked-out package so local changes are exercised and no package download is needed:
RENDER="npx egregore-artifacts@latest"
if [ -f packages/egregore-artifacts/bin/cli.js ] && \
[ -d packages/egregore-artifacts/node_modules/react ]; then
RENDER="node packages/egregore-artifacts/bin/cli.js"
fi
If the local package exists without dependencies, install its dependencies or
use the npx fallback. Do not block a render on optional connected services.
Render typed artifacts
Run the matching command:
$RENDER quest <quest-file>
$RENDER handoff <handoff-file>
$RENDER activity
$RENDER board
$RENDER network
$RENDER document <markdown-file>
Use the renderer's reported HTML path rather than guessing it.
For documents, walk the generative-UI synthesis graph in
packages/design-system/generative-ui/skill/SKILL.md: select one id each for
objective, audience, register, palette, and grammar from the document's
substance, record one line of judgment for each, resolve the brief, and pass it
with --brief. If that layer is unavailable, render without the brief.
Compose flagship documents
Composition is the default for a multi-section strategy, briefing, explainer,
analysis, decision document, or anything explicitly requested as composed,
presentable, client-facing, designed, or --compose. Use the fast renderer for
typed artifacts, short utility documents, --fast, or --floor.
For composition:
- Read the source document in full.
- Copy
.codex/skills/view/assets/compose-scaffold.htmlto/tmp/egregore-artifacts/composed-<slug>.html. - Fill every placeholder and walk the generative-UI graph for the manifest's register, palette, grammar, and trail.
- Transform rather than mirror the markdown:
- write a two-tone claim-led hero and italic standfirst;
- make section headings state findings, not repeat source headings;
- choose components by meaning: ledger for Q/A, claims for numbers, panels for options, steps for sequences, feature rows for capability/status, threads for decisions, gap cards for negatives, and a readout for the honest bottom line;
- create one anchored navigation item per composed section.
- Keep every theme-sensitive color as
var(--token). Never emit inline hex colors in composed content. Preserve the scaffold's no-flash theme restore,<html data-theme>, and light/auto/dark behavior. - Verify no placeholders remain, open the HTML with the platform browser
opener, and report
Renderer: composed (band 5, inline).
Publish the stable board
After $RENDER board, publish best-effort only when egregore.json declares a
connected configuration:
_API_URL=$(jq -r '.api_url // empty' egregore.json 2>/dev/null)
_MODE=$(jq -r '.mode // empty' egregore.json 2>/dev/null)
if [ -n "$_API_URL" ] && [ "$_MODE" != "local" ]; then
ORG_NAME=$(jq -r '.org_name // .slug' egregore.json)
bash bin/publish-artifact.sh board memory/board/board.json \
--id board \
--title "Project Board — $ORG_NAME" \
--author "$ORG_NAME" \
--description "Latest board for $ORG_NAME" 2>/dev/null &
fi
The local artifact remains the successful result if publishing fails. In local mode, do not call graph or notification services.
Report
Return only the useful receipt after the browser opens:
✓ Artifact opened in browser
File: /tmp/egregore-artifacts/<rendered-file>.html
For a connected board, append:
◆ https://egregore.xyz/view/<org-slug>/board (stable — refresh for latest)
Emit telemetry best-effort after completion:
bash bin/telemetry.sh emit "command" '{"command":"view"}' 2>/dev/null &
Rules
- Keep filesystem resolution sufficient in local mode; the graph is optional.
- Preserve auto-linked backtick references handled by
bin/publish-references.shwhen publishing markdown. - Never install a global renderer package as the first choice.
- Never call the deprecated
egregore-handoffCLI. - Never claim publishing succeeded unless a URL was actually returned.
When not to use it
- →When the user wants a prose summary instead of a visual artifact
- →When the user wants to delegate through Loom
Limitations
- →Does not invoke Claude Code commands
- →Does not delegate through Loom
- →Does not replace the artifact with a prose summary
How it compares
This skill renders Egregore data and documents as branded browser artifacts, preserving design and composition, unlike simply displaying raw content or prose summaries.
Compared to similar skills
view side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| view (this skill) | 0 | 1mo | No flags | Intermediate |
| readme-metrics-dashboard | 0 | 3mo | No flags | Beginner |
| operational-hydrologist | 0 | 4mo | No flags | Intermediate |
| memory-transform | 0 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by egregore-labs
View all by egregore-labs →You might also like
readme-metrics-dashboard
harrybin
Refresh repository metrics, render a full chart dashboard (line, bar, area, pie, scatter, composed), and update README with a reproducible example.
operational-hydrologist
hydrosolutions
Domain expert reviewer representing operational hydrologists in Central Asia, Nepal, Switzerland, and the Caucasus. Use when: (1) making frontend/dashboard changes targeted at hydrologists, (2) writing or updating documentation for end users, (3) reviewing forecast results and skill metrics after mo
memory-transform
fahad0001
Agent memory transformation skill. Converts the indexed agent memory into navigable representations including Obsidian vaults with backlinks, Mermaid dependency and status graphs, Graphviz DOT files, and static dashboards. Use when the user wants to visualize requirements, browse memory in Obsidian,
extract-tikz
alohays
Extract TikZ diagrams from Beamer source, compile to PDF, convert to SVG with 0-based indexing. Use when updating TikZ diagrams for Quarto slides.
streamlit
sverzijl
When working with Streamlit web apps, data dashboards, ML/AI app UIs, interactive Python visualizations, or building data science applications with Python
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.