jramsahai
- 16 skills
- 0 followers
- 4 hours ago last updated
- ▌ Vault Recall · jramsahaiAnswer questions from the Obsidian vault: "what do I know about X", "what did I discuss with [person]", "when/why did we decide Y", "summarize my week", project or topic history. Read-only search, reading, and synthesis across notes, links, and syntheses. NOT for: capturing or changing anything (use the routing skills), daily standup (standup), or vault reorganization (nightly-consolidation).
- ▌ Daily Journal · jramsahaiCapture personal daily diary entries in the Obsidian vault: mood, energy, weather, exercise, food, media, purchases, random thoughts. Use for "today I..." personal logs and observations. NOT for: reusable reference facts (knowledge-base), actionable work (task-tracking), project updates or conversation notes (project-tracking), or durable person context (people-notes).
- ▌ Idea Pipeline · jramsahaiCapture, compare, score, and pressure-test startup or product ideas before they become tracked work projects. Use when: (1) brainstorming candidate ideas, (2) comparing multiple directions, (3) building an idea scorecard, (4) evaluating whether an idea is worth deeper validation, or (5) deciding whether to promote an idea into a tracked project. NOT for: maintaining an active work project, project archival, or project-specific research after a tracked project has already been established.
- ▌ Meeting Notes · jramsahaiTurn a meeting transcript, dictated recap, or bullet notes (including voice bridge output) into a meeting note, project decisions, action items, and person conversation history. Owns ingestion of raw meeting/voice material only. NOT for: the meeting note's own shape or the project's sections (project-tracking), the person note's shape (people-notes), or task mechanics beyond adding the item (task-tracking).
- ▌ Shopping List · jramsahaiManage per-store shopping lists in the Obsidian vault. Use when: (1) adding items to buy at a store, (2) checking what's on a store's list, (3) marking items bought, (4) creating a list for a new store, (5) recurring shopping routines. NOT for: work projects, people tracking, general tasks with due dates (use task-tracking), or general note-taking.
- ▌ Task Tracking · jramsahaiManage centralized checkbox tasks in the Obsidian vault's Tasks.md: add, update, and complete tasks with due dates, priorities, waiting states, and project wikilinks. Use for anything actionable with an owner or deadline. NOT for: project status changes (project-tracking), store shopping items (shopping-list), or idea capture (idea-pipeline).
- ▌ Weekly Review · jramsahaiOnce-a-week pass over the Obsidian second brain: what shipped, what slipped, which projects went quiet, and three specific questions for the user. On demand ("run my weekly review") or by cron. Read-mostly, like standup, plus applying the user's own answers from last week's review. NOT for: daily status (standup), nightly linking and inbox triage (nightly-consolidation), or creating tasks/projects from scratch (task-tracking / project-tracking).
- ▌ Knowledge Base · jramsahaiCapture and organize evergreen reference notes in the Obsidian vault: facts, how-tos, techniques, recipes, product research, captured articles/videos/links. Use when info is reusable beyond today and not tied to a specific project, person, or day. NOT for: tasks or reminders (task-tracking), project state (project-tracking), diary entries (daily-journal), or conversations (people-notes).
- ▌ Project Tracking · jramsahaiTrack work projects in the Obsidian vault: create/update project notes, status, key decisions, blockers, meeting notes, docs, and stakeholder links. Use for project state and project conversations. NOT for: individual tasks (task-tracking), pre-project ideas (idea-pipeline), or evergreen reference (knowledge-base).
- ▌ Nightly Consolidation · jramsahaiNightly Obsidian vault consolidation (cron or on demand): triage inboxes, wikilink entity mentions, add related-note links, maintain MOCs, write a synthesis note. Connects and organizes existing notes only. NOT for: creating new facts, tasks, projects, or people, or any user-initiated capture (route those to the specialized skills).
- ▌ Goals · jramsahaiTrack what a project or set of projects is working toward: create a goal note, link a project to it, mark a goal achieved or dropped, and answer "how is <goal> going" by listing its projects and their status. Use when the user talks about a purpose or outcome, not just a piece of work. NOT for: project status, decisions, or blockers (project-tracking), or individual tasks (task-tracking).
- ▌ Standup · jramsahaiGenerate a standup summary from Obsidian project/task state, on demand or by cron: active projects, overdue and due-soon tasks, waiting states, stale items, pending conversations. Read-mostly synthesis. NOT for: changing task or project state (task-tracking / project-tracking).
- ▌ Resurfacing · jramsahaiMonthly pass (on demand or by cron) that finds projects, people, and knowledge notes that have gone quiet — no dated entry in 90+ days — and asks the user what to do with each: keep, archive, or link elsewhere. Read-mostly until the user answers; only then archives or links the specific notes named, and nothing else. NOT for: weekly project staleness at 14 days (weekly-review's Quiet Projects), who to reach out to at 60 days (people-notes -> Cadence), or nightly linking and inbox triage (nightly-consolidation).
- ▌ People Notes · jramsahaiTrack durable per-person notes in the Obsidian vault: conversation history, pending topics to discuss, relationship context, project associations. Use when info is about a person and worth keeping beyond today. NOT for: one-off diary mentions (daily-journal), project decisions (project-tracking), or action items (task-tracking).
- ▌ Second Brain · jramsahaiShared coordination layer for all Obsidian vault work: vault config, routing rules, frontmatter standards, wikilink conventions, the obsidian__ tool surface, and machine edit policy. Use alongside any second-brain skill and to decide which specialized skill handles a capture.
- ▌ Skill Tuning · jramsahaiMonthly pass (cron on the 1st at 09:00, or on demand) that reviews accumulated corrections, review answers, and retired link candidates, then proposes concrete SKILL.md wording changes for the user to review. Read-only: writes nothing to the vault and edits no skill file itself. NOT for: correcting a skill in the moment, nightly connection work (nightly-consolidation), or day-to-day vault writes (the specialized skills).