How do I install the Project Notes skill?

Run npx skillmds@latest add carlos-algms/project-notes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Project Notes safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Notes?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Project Notes free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Project Notes?

carlos-algms (@carlos-algms) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Project Notes by carlos-algms — Agent Skill

Name: Project Notes
Author: carlos-algms

Project Notes

Search, create or update durable repo-specific notes in the user's Obsidian vault. Use for investigations, decisions, failures and coding lessons tied to a repository. Use `second-brain` for reusable or personal knowledge.

carlos-algms 930b3b1 2.7 KB Updated Sep 17, 2026

File contents

Project notes

Store repo-specific provenance under 020-work/project-notes/<project-name>/.

Skill loading

Operation	Required skills
Choose the project-notes route	`project-notes` only
Search or read project notes	Add `obsidian-mechanics`
Create or edit a project note	Add `obsidian-mechanics` and `obsidian-markdown`
Discover or troubleshoot CLI use	Add `obsidian-cli`

Load each skill before its first matching operation. If the operation changes, load newly required skills before continuing. Never skip a required skill because its rules seem familiar or time is short.

Location

020-work/project-notes/<project-name>/YYYY-MM-DD-<topic-slug>.md

Derive the project name from the working-directory basename or context.
Create folders as needed.
Use date-first, globally unique filenames.

Frontmatter

---
title: Note Title
date: YYYY-MM-DD
tags:
  - project/project-name
  - topic-tag
type: project
status: active
aliases:
  - Alternate Name
---

No colons in title or aliases.
Put sources in ## Sources, not frontmatter.
Use inline wikilinks instead of related.
Use type: reference for reusable material scoped to one project and type: fleeting for temporary captures.

Content

Add an H1 and include the date in it or the first paragraph.
Record enough commands, errors, links and steps to reproduce an investigation.
Cite file paths and line numbers when available.
Apply the source convention from obsidian-mechanics.

Coding lesson

## YYYY-MM-DD - <symptom>

- Tool/cmd: `<failed command>`
- Error: <verbatim error>
- Cause: <root cause>
- Fix: <what worked>
- Lesson: <general rule>
- Tags: [tag-one, tag-two]

Decision

## YYYY-MM-DD - <decision>

- Status: accepted | superseded | deprecated
- Context: <constraint or trigger>
- Options: A) <...> B) <...>
- Decision: <choice>
- Rationale: <why>
- Consequences: <commitments>
- Revisit-when: <invalidation signal>

Give each lesson or decision its own date-prefixed note unless it belongs to the same subject captured that day. Never rewrite decision history; create a new note and link superseded decisions.

---name: project-notesdescription: Search, create or update durable repo-specific notes in the user's Obsidian vault. Use for investigations, decisions, failures and coding lessons tied to a repository. Use `second-brain` for reusable or personal knowledge.---# Project notesStore repo-specific provenance under `020-work/project-notes/<project-name>/`.## Skill loading| Operation | Required skills || -------------------------------- | ------------------------------------------------ || Choose the project-notes route | `project-notes` only || Search or read project notes | Add `obsidian-mechanics` || Create or edit a project note | Add `obsidian-mechanics` and `obsidian-markdown` || Discover or troubleshoot CLI use | Add `obsidian-cli` |Load each skill before its first matching operation. If the operation changes,load newly required skills before continuing. Never skip a required skillbecause its rules seem familiar or time is short.## Location```text020-work/project-notes/<project-name>/YYYY-MM-DD-<topic-slug>.md```- Derive the project name from the working-directory basename or context.- Create folders as needed.- Use date-first, globally unique filenames.## Frontmatter```yaml---title: Note Titledate: YYYY-MM-DDtags: - project/project-name - topic-tagtype: projectstatus: activealiases: - Alternate Name---```- No colons in `title` or `aliases`.- Put sources in `## Sources`, not frontmatter.- Use inline wikilinks instead of `related`.- Use `type: reference` for reusable material scoped to one project and `type: fleeting` for temporary captures.## Content- Add an H1 and include the date in it or the first paragraph.- Record enough commands, errors, links and steps to reproduce an investigation.- Cite file paths and line numbers when available.- Apply the source convention from `obsidian-mechanics`.### Coding lesson```markdown## YYYY-MM-DD - <symptom>- Tool/cmd: `<failed command>`- Error: <verbatim error>- Cause: <root cause>- Fix: <what worked>- Lesson: <general rule>- Tags: [tag-one, tag-two]```### Decision```markdown## YYYY-MM-DD - <decision>- Status: accepted | superseded | deprecated- Context: <constraint or trigger>- Options: A) <...> B) <...>- Decision: <choice>- Rationale: <why>- Consequences: <commitments>- Revisit-when: <invalidation signal>```Give each lesson or decision its own date-prefixed note unless it belongs to thesame subject captured that day. Never rewrite decision history; create a newnote and link superseded decisions.

Frequently asked questions