plugins/origin/skills/read/SKILL.md
Preview a distilled wiki page from inside Claude Code. Prints title, summary, source count, and the local md path. Full body lives on disk — open with the user's editor. Invoked as `/read <title_or_id>`.
npx skillsauth add davepoon/buildwithclaude readInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Surface a page's identity so the user can decide whether to open it.
/read is preview, not full text. The body is on disk; preview
keeps chat scannable, dodges Bash output truncation, and respects the
"md is canonical, viewer is the user's editor" model.
Two shapes accepted:
page_; legacy concept_ ids still work) → direct fetch.Both end with the same preview block.
Call the MCP tool to fetch the page:
get_page(page_id="<id>")
The response is a JSON object wrapping { "page": {...} }. Read
title, summary, space, and source_memory_ids off the page,
then look up the md filename in ~/.origin/pages/.origin/state.json:
Bash: python3 -c '
import json, os, sys
state_path = os.path.expanduser("~/.origin/pages/.origin/state.json")
pid = "<id>"
filename = None
try:
with open(state_path) as f:
filename = json.load(f).get("pages", {}).get(pid, {}).get("file")
except FileNotFoundError:
pass
print(f"~/.origin/pages/{filename}" if filename else "(no md projection on disk)")
'
Combine the page fields with the resolved md path and emit the preview block.
Search first, then fetch the top hit by id and run the same preview
block. Always resolve through the search_pages MCP tool — never
derive a slug client-side (skill heuristics drift from the canonical
slugify() on apostrophes and punctuation).
search_pages(query="<arg>", limit=1)
Parse the returned JSON — the response shape is { "pages": [...] }.
Read the first hit's id. If pages is empty, tell the user "no page
found matching <arg> — try /distill <arg> to create one" and stop.
Otherwise call get_page(page_id=<id>) and emit the same preview
block from section 1.
Always print exactly these lines (no body):
Title: <title>
Version: v<N> — <last_edited_by> <relative_time> (<last_delta_summary>)
Summary: <one sentence>
Sources: <N> memories
Space: <space or (none)>
Links: <N inbound, M outbound (<K> broken)>
Open: ~/.origin/pages/<slug>.md
⚠ Stale: <stale_reason> — run /distill to refresh
Lock banner rule:
When the page payload returned by get_page has user_edited == true,
prepend this line as the very first line of the rendered output, before
the title:
🔒 You've edited this page. Auto-refresh paused. `/distill rebuild <page-id>` to unlock.
Substitute <page-id> with the actual page.id value. When
user_edited is false or absent, omit this line entirely.
The lock means daemon distill cycles will not auto-rewrite this page's
prose from sources — edits stay until the user explicitly runs
/distill rebuild to wipe and regenerate.
Version line rules:
v<N>. When version is null or missing, omit the line. — <last_edited_by> when populated (e.g. re_distill, user, agent).last_edited_at is set (e.g. 2h ago, 3d ago).(<last_delta_summary>) when the field is non-empty.v1 — synthesized 4h agov4 — re_distill 2h ago (+mem_xyz, +250 chars)v3 — user 1d agoStale warning rule:
⚠ Stale: line only when stale_reason is non-null/non-empty.stale_reason verbatim (daemon sets it; values like
source_updated, new_memories are human-readable enough).Links line rules (unchanged): Call get_page_links(page_id="<id>") right after
get_page and count:
len(inbound)len(outbound)target_page_id is nullOmit the parenthetical when broken is zero. Drop the line entirely if inbound + outbound is zero.
Don't paraphrase the title, don't trim the summary, don't decorate the preview. The block is one screen, predictable, easy to skim.
If the user wants the full body, they open the md file in their editor (Obsidian, VS Code, glow, bat, …). The plugin doesn't render markdown better than their tools do.
/distill finishes, follow up with /read "<title>" (titles
survive any rendering surface; ids may visually truncate)./recall.list_pages_recent MCP tool or
ls ~/.origin/pages/.tools
Assesses the current state of the startup project and recommends what to focus on next. Use when there is a need or a question from the user to understand what the next steps are or what to focus on next.
data-ai
Use at the start of any conversation about a startup idea, product validation, founder strategy, or work inside a `startup/` workspace. Establishes file conventions, voice-input handling, subagent dispatch rules, and how to update each artifact safely. Activate before invoking any other startup-superpowers skill.
tools
Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses. Use when the founder wants to run a survey, create survey questions, validate hypotheses at scale, check how a survey is going, understand whether a survey is the right tool right now, or deploy a question set to get quantitative signal. Also bring this up if you believe that creating a survey to collect quantitative evidence may be useful at this point.
development
Guides the founder through designing and optionally building the simplest MVP or prototype that validates their current hypotheses. Use when the founder wants to build something to test assumptions, discusses what to build next, wants to interpret results from a live MVP, or is deciding whether the current approach is still right. Also use when a founder proposes something to build — the skill will check whether the proposed form is the simplest thing that generates honest signal.