plugins/origin/skills/help/SKILL.md
One-screen quick reference for the Origin plugin. Lists the daily verbs, the daily flow, where data lives, and how to view it without a GUI. Use when the user says "help", "what can I do", "list origin commands", "how do I use origin", or invokes `/help`.
npx skillsauth add davepoon/buildwithclaude helpInstall 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.
Print the Origin plugin reference card. Read-only — never calls a tool.
When triggered, output the block below verbatim. No editing, no abbreviating, no embellishing. The user is asking for the menu.
Origin plugin — daily verbs
/init set up Origin (auto-installs daemon + local memory)
/brief load identity + topic context (start of session)
/capture <x> save one durable memory in flow
/recall <q> search local memory
/distill [t] synthesize pages from clusters (scoped to current repo)
/read <p> preview a distilled page inline
/review <surface> deep audit (surface = captures|revisions); /brief handles daily
/forget <id> delete a memory by ID
/handoff end-of-session ritual (session log + captures)
/debrief alias for /handoff (brief/debrief symmetry)
/help this card
Daily flow (~1 min overhead per session):
1. start session → hook auto-checks daemon, silent if up
2. /brief → ~5 s, load context
3. work normally → Claude proactively /captures durable facts
4. /recall X → as needed for lookups
5. /handoff → ~30 s, narrative session log + captures
Where your data lives (everything under ~/.origin/):
~/.origin/pages/ wiki pages distilled from your memories (md)
~/.origin/sessions/ session logs by date (md)
~/.origin/sessions/_status/ current per-project goals + last-handoff
~/.origin/db/ memories + knowledge graph (symlink to libSQL)
~/.origin/bin/ installed binaries
View it without a GUI:
open ~/.origin/ browse in Finder
code ~/.origin/ open in VS Code
git -C ~/.origin log --oneline timeline of every memory + distill pass
ln -s ~/.origin/pages ~/Vault/origin # symlink into Obsidian for graph view
~/.origin/ is a git repo. Skills auto-commit per logical batch (one per
session, distill pass, or forget). Use git log / git diff / git revert
as a free audit trail. No remote — purely local history.
Three classes of artifact:
- memories: granular, queryable, live in DB only (confirmed = stays in DB)
- pages: synthesized wikis, DB + ~/.origin/pages/*.md projection
- sessions: chronological narrative, ~/.origin/sessions/*.md only
Daemon must run at 127.0.0.1:7878. Hook prints "/origin:init" if down.
Optional upgrades for richer distill cycles:
origin model install local Qwen, no API cost
origin key set anthropic Anthropic API, higher quality
/help./init success too./recall./init (it diagnoses + auto-installs).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.