Agent skill

Obsidian Log

by grandamenium in grandamenium/cortextos

Write key decisions, project milestones, and feedback rules back to the Obsidian vault.

MITAuto-check passedProduct & Project Management

Install Obsidian Log

skills CLI
$ npx skills add grandamenium/cortextos --skill obsidian-log -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install grandamenium/cortextos obsidian-log --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/grandamenium/cortextos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/community/skills/obsidian-log .claude/skills/obsidian-log && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
obsidian-log
GitHub stars
101
Token cost
~1k tokens
SKILL.md length
303 words
Files
1
Skills in repo
55
Repo updated
First seen
Licence
MIT

At a glance

Write key decisions, project milestones, and feedback rules back to the Obsidian vault.

  • Works in 3 steps: Log a decision (daily decisions log) → Log a project milestone → Log a durable feedback rule
  • Tasks that involve Project management
  • SKILL.md covers When to Use, CLI Reference, Workflow and Keep the KB Current, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Obsidian Log is an agent skill from grandamenium/cortextos. Write key decisions, project milestones, and feedback rules back to the Obsidian vault. Use this after confirming any architectural decision, project milestone, or durable feedback rule — keeps the vault current with agent memory.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Project management and Agent memory. It works with Obsidian. The licence is MIT.

When your agent uses it

  • Tasks that involve Project management
  • Tasks that involve Agent memory

Example prompts

  • “/obsidian-log”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Log a decision (daily decisions log)
  2. Log a project milestone
  3. Log a durable feedback rule

What it can do on your machine

Read from SKILL.md and the folder at commit 6f93838. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Obsidian Log loads about 1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 303 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from grandamenium/cortextos at commit 6f93838, republished under its MIT licence (© grandamenium). 303 words, ~1,047 tokens.

Download SKILL.mdSave it as .claude/skills/obsidian-log/SKILL.md (or your agent's skills folder).
name
obsidian-log
description
Write key decisions, project milestones, and feedback rules back to the Obsidian vault. Use this after confirming any architectural decision, project milestone, or durable feedback rule — keeps the vault current with agent memory.
effort
low
triggers
obsidian, write to vault, log decision, save to obsidian, update vault, obsidian log, decision log, vault write-back, milestone logged, write back, obsidian…

Obsidian Log Skill

Write agent decisions and milestones back to the Obsidian vault so it stays current with agent memory. Use after confirming any significant decision, project milestone, or durable feedback rule.


When to Use

Trigger this skill when you:

  • Confirm an architectural or product decision (e.g. "we decided X approach for Y")
  • Complete a project milestone and want it recorded (e.g. "feature Z shipped")
  • Receive and confirm a durable feedback rule (e.g. "always do X, never do Y")
  • Finish an onboarding or knowledge distillation session

Do NOT log every task or message — only decisions and milestones that should persist across agents and sessions.


CLI Reference

The Obsidian CLI writes directly to vault notes. Replace [VAULT_NAME] with your configured vault name.

Create or overwrite a note
bash
obsidian vault=[VAULT_NAME] create path="<note-path>" content="<content>" overwrite
Append to an existing note
bash
obsidian vault=[VAULT_NAME] append path="<note-path>" content="<content>"

Workflow

1. Log a decision (daily decisions log)

Decisions go to 01-Memory/decisions-YYYY-MM-DD.md. Append so the daily file accumulates entries:

bash
TODAY=$(date +%Y-%m-%d)
obsidian vault=[VAULT_NAME] append \
  path="01-Memory/decisions-${TODAY}.md" \
  content="
## [HH:MM] <Decision title>

**Decision:** <What was decided>
**Why:** <Reasoning or constraint that drove it>
**Impact:** <What changes as a result>
**Agent:** [AGENT_NAME]
"

If the daily file does not exist yet, use create instead of append:

bash
TODAY=$(date +%Y-%m-%d)
obsidian vault=[VAULT_NAME] create \
  path="01-Memory/decisions-${TODAY}.md" \
  content="# Decisions — ${TODAY}

## [HH:MM] <Decision title>

**Decision:** <What was decided>
**Why:** <Reasoning or constraint that drove it>
**Impact:** <What changes as a result>
**Agent:** [AGENT_NAME]
" overwrite
2. Log a project milestone

Project milestones append to 02-Projects/<project-name>.md:

bash
obsidian vault=[VAULT_NAME] append \
  path="02-Projects/<project-name>.md" \
  content="
## Milestone — $(date +%Y-%m-%d)

**What shipped:** <Feature or deliverable>
**Status:** Complete
**Notes:** <Any relevant context>
"
3. Log a durable feedback rule

Feedback rules that should persist append to 01-Memory/agent-feedback.md:

bash
obsidian vault=[VAULT_NAME] append \
  path="01-Memory/agent-feedback.md" \
  content="
## $(date +%Y-%m-%d) — <Rule title>

**Rule:** <The feedback rule>
**Why:** <Reason given by user or inferred>
**Agent:** [AGENT_NAME]
"

Keep the KB Current

After writing to the vault, ingest the updated memory folder so agents can find it via KB search:

bash
cortextos bus kb-ingest <vault-path>/01-Memory --org [ORG] --scope shared

You can also add a daily cron entry to config.json to keep the KB automatically current:

json
{
  "name": "daily-memory-kb-ingest",
  "cron": "0 4 * * *",
  "prompt": "Ingest today's memory files into the KB: cortextos bus kb-ingest <vault-path>/01-Memory --org [ORG] --scope shared. Log the result.",
  "type": "recurring"
}

Checklist Before Writing

  • Is this a decision, milestone, or feedback rule — not just a task update?
  • Does the vault path match the correct date / project name?
  • Use append if the file exists, create with overwrite if starting fresh for the day
  • Ingest 01-Memory/ after writing so the KB reflects the new entry

Deployment note: replace [VAULT_NAME], [AGENT_NAME], and [ORG] with your actual values. Add the vault path to your agent's TOOLS.md so it is available at session start.

© grandamenium, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in community/skills/obsidian-log of grandamenium/cortextos.

Open the folder on GitHubat commit 6f93838

Compare with similar skills

Obsidian Log next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Obsidian Log compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Obsidian Log this skillgrandamenium/cortextos101—~1kAutomated safety check: PassMIT
Project Managerespennilsen/pi122—~2.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Qmdbreferrari/obsidian-mind5k—~1.7kAutomated safety check: PassMIT
Agent RecallGoldentrii/AgentRecall-X371—~5.2kAutomated safety check: NotesMIT
Jira Natural Language Interfacejjmartres/opencode1333 repos~1.7kAutomated safety check: PassMIT

Similar skills

  • Project Manager

    espennilsen/pi

    Manage Espen's projects across the Dev folder and Obsidian vault.

    122 GitHub stars~2.1k tokensUpdated 19 days ago
    Product & Project ManagementAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Qmd

    breferrari/obsidian-mind

    Search the vault using QMD semantic search. An agent skill from breferrari/obsidian-mind.

    5k GitHub stars~1.7k tokensUpdated 5 days ago
    Agent WorkflowsAuto-check passed
  • Agent Recall

    Goldentrii/AgentRecall-X

    Persistent compounding memory for AI agents. An agent skill from Goldentrii/AgentRecall-X.

    371 GitHub stars~5.2k tokensUpdated 13 days ago
    Agent WorkflowsAuto-check: notes
  • Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.

    133 GitHub starsUsed in 3 repos~1.7k tokens
    Product & Project ManagementAuto-check passed
  • Project Planner

    adrianpuiu/claude-skills-marketplace

    Comprehensive project planning and documentation generator for software projects.

    100 GitHub starsUsed in 1 repo~6k tokens
    Product & Project ManagementAuto-check passed

More from grandamenium/cortextos

All 55 skills in this repo
  • Cortext Self Diagnosis

    grandamenium/cortextos

    Diagnose cortextOS itself when the framework misbehaves — an agent has gone silent or wedged, agents are crash-looping, Telegram or agent-to-agent messages are not arriving, crons did not fire, an…

    101 GitHub stars~3.7k tokensUpdated 18 days ago
    Auto-check passed
  • Activity Channel

    grandamenium/cortextos

    You have completed something significant and want the whole org — all agents and the user — to know about it.

    101 GitHub stars~624 tokensUpdated 18 days ago
    Auto-check passed
  • Agentcard Purchase

    grandamenium/cortextos

    You need to make a purchase on behalf of the user — buy a SaaS subscription, pay for an API, purchase a domain, or any transaction requiring a credit card.

    101 GitHub stars~1.1k tokensUpdated 18 days ago
    Auto-check passed
  • Claude To Codex Migration

    grandamenium/cortextos

    Migrate ANY cortextOS agent from the claude-code runtime to the live codex-app-server runtime.

    101 GitHub stars~12k tokensUpdated 18 days ago
    Auto-check: warnings
  • Bus Reference

    grandamenium/cortextos

    Complete cortextos bus CLI reference - all available commands with examples.

    101 GitHub stars~3.8k tokensUpdated 18 days ago
    Auto-check passed
  • Business News Monitor

    grandamenium/cortextos

    Daily cron-driven scan of news/forums/social in a domain to surface market shifts, new competitors, regulatory changes, and net-new opportunities.

    101 GitHub stars~1.3k tokensUpdated 18 days ago
    Auto-check passed

Works with

Questions about Obsidian Log

What does Obsidian Log do?

Write key decisions, project milestones, and feedback rules back to the Obsidian vault. Obsidian Log is an agent skill from grandamenium/cortextos. Write key decisions, project milestones, and feedback rules back to the Obsidian vault.

When should I use Obsidian Log?

Obsidian Log fits situations like: tasks that involve Project management; tasks that involve Agent memory.

How do I install Obsidian Log in Claude Code?

Run `npx skills add grandamenium/cortextos --skill obsidian-log -a claude-code`. Or copy the skill folder (community/skills/obsidian-log in grandamenium/cortextos) into .claude/skills/obsidian-log in your project. Claude Code loads it when a task matches its description.

How do I install Obsidian Log in Codex?

Run `npx skills add grandamenium/cortextos --skill obsidian-log -a codex`. Or copy the skill folder (community/skills/obsidian-log in grandamenium/cortextos) into .agents/skills/obsidian-log in your project. Codex loads it when a task matches its description.

Can I use Obsidian Log in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add grandamenium/cortextos --skill obsidian-log -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/obsidian-log, .gemini/skills/obsidian-log, .github/skills/obsidian-log and .opencode/skills/obsidian-log in your project.

What does Obsidian Log need to run?

SKILL.md names no scripts, command-line tools or credentials: Obsidian Log is instructions for the agent only.

Does Obsidian Log access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Obsidian Log safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Obsidian Log use?

Obsidian Log is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Obsidian Log use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Obsidian Log?

Skills that share tags, products or a category with Obsidian Log: Project Manager (espennilsen/pi, 122 stars), CCPM Project Management (automazeio/ccpm, 8.4k stars), Qmd (breferrari/obsidian-mind, 5k stars) and Agent Recall (Goldentrii/AgentRecall-X, 371 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Obsidian Log?

grandamenium (a GitHub user) maintains it in grandamenium/cortextos, which has 101 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on September 23, 2026.

Source: grandamenium/cortextos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.