paperclip-api
Use when managing Paperclip AI agent companies - creating tasks, managing agents, approving hires, running heartbeats, or any Paperclip control-plane…
Use when capturing ONE new idea the user voices and wants recorded — "save this idea", "I have an idea", "log this idea", "/idea", "idea: ...". Creates a provenance-tracked folder (one folder per idea) in your ideas repo, dedups against an index, optionally mirrors to a GitHub
$ npx -y skills add serejaris/personal-corp-os --skill idea --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/ideaContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when capturing ONE new idea the user voices and wants recorded — "save this idea", "I have an idea", "log this idea", "/idea", "idea: ...". Creates a provenance-tracked folder (one folder per idea) in your ideas repo, dedups against an index, optionally mirrors to a GitHub
name: idea description: >- Use when capturing ONE new idea the user voices and wants recorded — "save this idea", "I have an idea", "log this idea", "/idea", "idea: ...". Creates a provenance-tracked folder (one folder per idea) in your ideas repo, dedups against an index, optionally mirrors to a GitHub Project view filtered by label:idea. NOT for mining ideas out of transcripts/meetings (use a dedicated extraction skill) and NOT for dated work tasks (use an issue tracker / the manager skill). Triggers also in Russian: «запиши идею», «у меня идея», «зафиксируй идею».
Part of the Personal Corp framework — running a one-person business through AI agents.
One pipeline: your voice → a provenance-tracked folder in your ideas repo → (optional) an issue mirror on a GitHub Project view. The folder is the source of truth; everything else is a pointer to it.
This skill is **self-contained** — it inlines the folder structure, status enum, and provenance formats below. You don't need any external canon file.
Before first use, define this in your project's `CLAUDE.md`:
## Idea Config ### Ideas repo path Where idea folders live (one folder per idea): - ideas_repo: ~/Projects/ideas ### Default author Name written into `first_voiced_by` when the user doesn't say otherwise: - default_author: Me ### GitHub mirror (optional) Mirror each idea as an issue (added to a Project view filtered by `label:idea`): - mirror_enabled: false - owner: your-github-handle # only if mirror_enabled: true - ideas_repo_name: ideas # GitHub repo name for the issue, only if mirror_enabled: true - project_number: <your Project number> # only if mirror_enabled: true (if mirror_enabled is false, the skill only writes to the ideas repo — no issue, no Project)
No separate init skill needed — this section is the setup. If `mirror_enabled` is false, the GitHub Project step is skipped entirely; the idea still lives as a folder.
Ask **at most one** short question, and only if the idea's essence can't be extracted from the wording (what is it / for whom). Do NOT ask about mechanics, pricing, risks, or tech stack — capture the raw material as-is and write the gaps into `next-steps.md` as open questions. The question **"how should I record it — issue / file / both?"** is forbidden: the form is fixed by this skill. Never block on form.
A freshly captured idea is always `seedling`.
Every idea needs at least one source. Each sighting is one row. Genericize the source kind — no real internal paths:
| Source kind | Format in `sources.md` | |---|---| | Meeting note | `meeting note — {who/where}, {date}` | | CRM card | `CRM card — {contact}, {date}` | | DM | `DM — {channel}, {date}` | | Voice draft (solo) | `voice draft, {date}` | | Reading / web | `{url}, {date}` | | Direct capture | `direct /idea invocation, session, {date}` |
1. **`date`** — resolve the real date. Between 00:00–04:00, "today" means the previous calendar day.
2. **Dedup against the index.** Read `INDEX.md` at the root of your ideas repo. Match is **semantic, not string** ("a board of advisors run on agents" ≈ `advisory-agent-grounded-data`). If unsure, open the candidate's `idea.md` to compare.
3. **New idea** → create the folder `ideas/YYYY-MM-DD-{slug}/` with the template files below.
4. **Regenerate `INDEX.md`** (format below). It's auto-generated — don't hand-edit individual rows; rewrite the whole file from the folders.
5. **GitHub Project mirror — OPTIONAL** (only if `mirror_enabled: true` in config). The folder is the source of truth; the issue is just a pointer for board view. See "Project mirror" below.
6. **Commit + push** to the ideas repo: `feat: idea {slug}` (invoking this skill is consent to record; the ideas repo is private).
7. **Report** — one line per item: folder path, issue `#N` (if mirrored), and the Project view link (if mirrored).
Create these four files in `ideas/YYYY-MM-DD-{slug}/`.
Personal Corp is a way to run a one-person company through AI agents: tasks out of your head, departments instead of one person's memory, a weekly retro instead of "I'll sort it out someday".
Use when managing Paperclip AI agent companies - creating tasks, managing agents, approving hires, running heartbeats, or any Paperclip control-plane…
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
Use when user asks for Claude Code usage stats, weekly analytics, project activity summary, or wants to see what projects were worked on. Triggers on…
Use when needing strategic project analysis from multiple independent expert perspectives. Triggers on business decisions, growth strategy, product direction,…
Use when creating or refactoring CLAUDE.md files - enforces best practices for size, structure, and content organization
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp-* owner…