memory-system

Use Obsidian as Claude's primary workspace and persistent memory. Activates for ALL file operations during sessions - working notes, scratchpads, analysis, task tracking - not just permanent knowledge. Prefer Obsidian MCP tools over local disk writes. Use proactively for any information worth preserving beyond the current conversation turn.

Ir para a instalação

Repositório: cajias/claude-skills
Última atividade na origem: 20 de julho de 2026 às 10:57
Idioma detectado do SKILL.md: inglês
Estrelas: 0
Forks: 0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/cajias/claude-skills --skill memory-system

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

milestone-goal-prompt

Research (as an internal step) a GitHub/GitLab milestone's open issues in order to PRINT a copy-paste autonomous-loop prompt that drives the milestone to completion — behavior-driven (BDD) scenarios, adversarial gap-checking, a per-iteration Definition-of-Done gate (build + all tests + zero lint + /code-review + /security-audit + /ponytail:ponytail findings all cleared), specialized-agent selection with model tier scaled to task complexity, and a root-cause→harness-hardening loop. Use this whenever the user says "generate a goal prompt", "goal-driven prompt", "milestone loop prompt", "prompt to finish/complete the milestone", "clear-and-paste prompt for milestone N", "make me a prompt to drive /autoresearch", or otherwise wants a ready-to-paste block that autonomously completes a milestone's remaining issues. The deliverable is the prompt itself, not a summary. NOT for actually executing the work (this only GENERATES and PRINTS the prompt — the loop does the work), NOT for merely summarizing or listing a mile

2026-08-13

apm-marketplace-authoring-gotchas

Eight APM-marketplace-authoring gotchas discovered during real migrations from hand-authored .claude-plugin/marketplace.json to APM-managed and from CC-native plugin authoring. Use when: (1) running APM's packaging step (with or without `--dry-run`) or its marketplace-check command in a repo with an `apm.yml`; (2) wiring CI for an APM marketplace; (3) the CI staleness check (repack, then `git diff --quiet`) fails despite a clean local; (4) prettier reformats `marketplace.json` after APM's packer writes it; (5) APM exit code 1 on local-path-only marketplaces; (6) confused by `packages:` in apm.yml vs `plugins:` in marketplace.json; (7) commitlint rejects a commit with `footer-leading-blank` despite no apparent footer; (8) `apm compile -t claude` exits 0 with zero output and no compiled plugin appears; (9) husky+lint-staged pre-commit blocks the FIRST marketplace commit with markdownlint `MD040/fenced-code-language` errors on a SKILL.md file copied verbatim from `~/.claude/skills/`. The gotchas form a chain — f

2026-07-21

apm-plugin-distribution-paths

Canonical authoring layout for an APM (microsoft/apm) package, plus the decision matrix for whether you need a `marketplace:` block. Use when: (1) you've run `apm init` and are unsure where SKILL.md / agent .md / command .md files belong (answer: under `.apm/`, NOT at repo root); (2) you've authored CC-native files at `commands/agents/skills/` at repo root and wonder if that's "right" (it works as fallback layout #3 "Claude plugin", but it's not the canonical authoring path); (3) you're trying to choose between the three layouts APM recognizes (one-skill repo, multi-primitive `.apm/`, Claude plugin); (4) `apm targets` fails with "No such command" in CLI 0.12.1 (subcommand doesn't exist); (5) `apm validate` fails with "No such command" in CLI 0.12.1 (use APM's packaging command in dry-run mode instead); (6) wondering whether `apm compile -t claude` will generate output for a hand-authored CC-native plugin (it won't; it's a no-op for layout #3); (7) wondering if you need a `marketplace:` block in apm.yml (you d

2026-07-21

Ver todas deste repositório

name	memory-system
description	Use Obsidian as Claude's primary workspace and persistent memory. Activates for ALL file operations during sessions - working notes, scratchpads, analysis, task tracking - not just permanent knowledge. Prefer Obsidian MCP tools over local disk writes. Use proactively for any information worth preserving beyond the current conversation turn.
version	2.0.0

Aspect	Local Disk	Obsidian
Folder creation	Need `mkdir` first	Auto-created
Searchability	Grep/Glob	`search_notes` with frontmatter
User visibility	Hidden in filesystem	Visible in Obsidian app
Cross-session	Lost or scattered	Organized, persistent
Linking	None	`[[wiki-links]]` work

Need	Tool	Example
Create/overwrite	`write_note`	Session context, scratchpad
Surgical edit	`patch_note`	Update status, add findings
Read	`read_note`	Load previous context
Search	`search_notes`	Find related work
List	`list_directory`	Browse folder contents

File	Purpose
`context.md`	Session state, current task, status
`scratchpad.md`	Working notes, analysis, draft content
`findings.md`	Discoveries, results, outputs
`tasks.md`	Task tracking if complex

Trigger	What to Capture	Where
Starting any task	Session context	`agent-workspaces/claude-[timestamp]-[context]/`
"Let's do X instead of Y"	Decision + rationale	`decisions/` folder as ADR
"I prefer..."	User preference	`agent-workspaces/shared/persistent.md`
"That worked/didn't work"	Lesson learned	`knowledge-base/lessons-learned/`
Person mentioned	Facts about them	`people/[name].md`
Recurring pattern	Pattern documentation	`knowledge-base/` with `#pattern`
Important constraint	Project context	`engagements/active/[project]/`
Quick note, unsure where	Inbox for triage	`agent-workspaces/shared/inbox.md`

Category	Tags
Status	`#draft` `#active` `#completed` `#archived`
Type	`#decision` `#pattern` `#lesson` `#meeting` `#blocker`
Priority	`#urgent` `#backlog`
Sharing	`#shareable` `#internal` `#sensitive`

memory-system

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Obsidian Memory System

Why Obsidian Over Local Disk

MCP Tools for Workspace

Session Workspace Protocol

1. Create Session Folder (Auto-Created)

2. Standard Session Files

3. Update Status When Done

When to Write to Obsidian

Always (Proactive)

During Complex Tasks

When to Read from Obsidian

Before Starting Work

Resuming Work

Write Location Decision Tree

Standard Frontmatter

Shared Persistent Context

Tag Taxonomy

What NOT to Store in Obsidian

Related