Turn your notes into a personal wiki kept up to date by a coding agent
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 agent.
Methods
Have a coding agent build and maintain a wiki of your notes
Steps
- Put the folder under git and split raw from wiki. Create raw/ and wiki/, add wiki/index.md and wiki/log.md, and commit. Make raw/ read-only in the schema rules. Check: git status is clean and the two folders exist.
- Write the schema with the agent. Ask the agent to propose the schema: page types, naming, links, source citations, conflicts, and the ingest, query and lint steps. Edit it until it matches how you think. Check: The schema is short, and you agree with every rule in it.
- Ingest one source and review the diff. Run the ingest prompt on one source. Read every changed page in the diff before you commit. Check: Each new fact links to its source, and no page was duplicated.
- Ingest in small batches. Add sources one at a time or a few at a time, committing after each. Large batches make diffs hard to review. Check: Each commit holds one ingest and its log line.
- Query the wiki, and file good answers back. Ask questions against the wiki. When an answer is useful, ask the agent to save it as a page with links to the pages it used. Check: Answers cite wiki pages, and those pages cite raw sources.
- Lint on a schedule. Run a lint pass weekly or after every ten sources: orphan pages, dead links, duplicate entities and stale reference sections. Approve fixes one by one. Check: The lint report shrinks over time and you approved each fix.
- Add search when the wiki outgrows the index. When the index and pages no longer fit the agent's context, add per-folder indexes or a local search tool, and keep the wiki as the main record. Check: The agent still finds the right pages for your questions.
- Optional: The source includes a Claude Code ingest prompt; it is linked there, not copied here.
- Note: Steps quoted from the Agents Handbook (CC BY 4.0). Works with Claude Code, Codex, Claude Cowork or Gemini CLI. Review each diff before you commit.
Run this method with your agent
Download .mdCopied 0
--- name: "agent-maintained-personal-wiki-method" description: "Use when you need to Turn your notes into a personal wiki kept up to date by a coding agent. Have a coding agent build and maintain a wiki of your notes" --- # Have a coding agent build and maintain a wiki of your notes Job: [Turn your notes into a personal wiki kept up to date by a coding agent](https://aiagents.org/canai/agent-maintained-personal-wiki) ## Need - AI agent ## Steps 1. Put the folder under git and split raw from wiki. Create raw/ and wiki/, add wiki/index.md and wiki/log.md, and commit. Make raw/ read-only in the schema rules. Check: git status is clean and the two folders exist. 2. Write the schema with the agent. Ask the agent to propose the schema: page types, naming, links, source citations, conflicts, and the ingest, query and lint steps. Edit it until it matches how you think. Check: The schema is short, and you agree with every rule in it. 3. Ingest one source and review the diff. Run the ingest prompt on one source. Read every changed page in the diff before you commit. Check: Each new fact links to its source, and no page was duplicated. 4. Ingest in small batches. Add sources one at a time or a few at a time, committing after each. Large batches make diffs hard to review. Check: Each commit holds one ingest and its log line. 5. Query the wiki, and file good answers back. Ask questions against the wiki. When an answer is useful, ask the agent to save it as a page with links to the pages it used. Check: Answers cite wiki pages, and those pages cite raw sources. 6. Lint on a schedule. Run a lint pass weekly or after every ten sources: orphan pages, dead links, duplicate entities and stale reference sections. Approve fixes one by one. Check: The lint report shrinks over time and you approved each fix. 7. Add search when the wiki outgrows the index. When the index and pages no longer fit the agent's context, add per-folder indexes or a local search tool, and keep the wiki as the main record. Check: The agent still finds the right pages for your questions. 8. Optional: The source includes a Claude Code ingest prompt; it is linked there, not copied here. 9. Note: Steps quoted from the Agents Handbook (CC BY 4.0). Works with Claude Code, Codex, Claude Cowork or Gemini CLI. Review each diff before you commit. ## Credit Method author Agents Handbook editors (CC BY 4.0) Source: https://agentshandbook.com/p/build-a-personal-knowledge-base-wiki-from-your-notes
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/agent-maintained-personal-wiki - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "agent-maintained-personal-wiki",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}