render-output
Skill1 starsChanged 7 months agoMITView on GitHub
Convert vault content into downstream outputs like memos, reports, slide outlines, diagrams, and plot specifications.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- compile-wikiSkill
- ingest-sourcesSkill
- lint-healSkill
- qa-agentSkill
- research-workflowSkill
The file
Files
Render Output
Goal
Transform the current vault into human-facing deliverables.
Common outputs
- executive memo
- research brief
- slide outline (structured markdown outline, not a binary file)
- architecture note
- comparison table
- Mermaid diagram spec
Rules
- Deliverables must be strictly grounded in the vault. Do not introduce outside information.
- Include a "Source Map" section at the end of the rendered document, detailing which Concept pages and Source summaries (with Obsidian wikilinks) informed the content.
- Save all rendered outputs under the
outputs/directory with a clean, lowercase, hyphenated filename (e.g.outputs/multi-agent-orchestration-slides.md). - Print the file paths of all generated files when done.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

