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.zip

Installs 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.
54 charsno explicit “when” trigger
Intermediate

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

You give it
User's request to view or render a document, quest, or board
You get back
A browser artifact (HTML file) and a compact receipt with the file path

When to use view

  • →View a quest
  • →Open project docs
  • →Render network state

About this skill

<!-- generated-by: bin/codex-sync-skills.sh -->

Egregore view Adapter

This adapter runs the canonical Egregore workflow for view. Its one maintained body is .claude/skills/view/SKILL.md; read that file completely and follow it here.

Use the project shell and filesystem directly. Do not invoke Claude Code commands. Translate interactive choices to structured Codex question tooling when it is available; otherwise render compact numbered choices with an Other: option and wait for the user.

Structured UX parity

This workflow has a Claude skill with user-visible structured output. After reading .claude/skills/view/SKILL.md, reproduce the same visible UX in Codex:

  • Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering, exact confirmation blocks, and "no preamble" rules from the source skill.
  • Use the source skill's frame width, section order, labels, status footer, and examples as the contract for the final response.
  • Never replace a required box/table/card/artifact view with a prose summary unless the user explicitly asks for a summary.
  • When the source says to output a TUI box directly, paste that box as the visible response, preferably in a text fenced block.
  • If the canonical body says the command's stdout is the card and must not be repeated, that rule assumes a host that displays command output in full; in Codex, paste the card once as the visible response in a text fenced block and do not print it a second time.
  • Never show raw JSON, raw command output, or unformatted script output when the source skill requires formatted status or rendered output.
  1. Read .claude/skills/view/SKILL.md for the workflow details.
  2. Run the referenced bin/ scripts directly from Codex.
  3. Treat graph and publish steps as best-effort unless that workflow explicitly says they are required.
  4. For every external notification, follow .claude/context/notification-consent.md: plan without sending, then show a separate exact Send / Edit / Cancel checkpoint. Never infer notification consent from the workflow request or a batch approval.
  5. Keep local-mode behavior filesystem-first and avoid graph or notification calls when egregore.json declares "mode": "local".
  6. Never call the deprecated egregore-handoff CLI for Egregore project handoffs.

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.

SkillInstallsUpdatedSafetyDifficulty
view (this skill)04moNo flagsIntermediate
readme-metrics-dashboard06moNo flagsBeginner
operational-hydrologist07moNo flagsIntermediate
memory-transform05moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

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.

00

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

00

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,

00

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.

00

streamlit

sverzijl

When working with Streamlit web apps, data dashboards, ML/AI app UIs, interactive Python visualizations, or building data science applications with Python

86239

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.

25170

Search skills

Search the agent skills registry