Captures project-specific conventions as lightweight YAML instincts to ensure consistency across your session.

Install

mkdir -p .claude/skills/instincts && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11841" && unzip -o skill.zip -d .claude/skills/instincts && rm skill.zip

Installs to .claude/skills/instincts

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Atomic behavioral instincts system. Captures micro-learnings as lightweight YAML entries with confidence scoring (0.3-0.9). Project-scoped instincts are stored locally; universal instincts feed into the reflect-kb GraphRAG knowledge base for cross-project retrieval. Use when: (1) A behavioral pattern should be remembered but is too small for a full learning note, (2) Building up project-specific conventions, (3) User wants quick lightweight corrections captured, (4) Accumulating micro-patterns during a session, (5) User requests /instincts.
546 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Capture micro-learnings as YAML entries with confidence scores.
  • Store project-scoped instincts locally in a YAML file.
  • Promote high-confidence universal instincts to a global knowledge base.
  • Review and adjust the confidence of existing instincts.
  • Remove low-confidence or stale instincts.
  • Apply instincts as soft rules at the start of a session.

How it works

The skill captures micro-learnings as YAML entries with confidence scores, storing project-scoped instincts locally and promoting high-confidence universal instincts to a global knowledge base.

Inputs & outputs

You give it
User correction or repeated observation
You get back
YAML entry in .agents/instincts.yaml with a confidence score

When to use instincts

  • Enforcing project-specific linting rules
  • Tracking preferred package managers (npm vs pnpm)
  • Recording recurring API data structures
  • Managing session-level coding preferences

About this skill

Instincts — Atomic Behavioral Micro-Learnings

Philosophy

Not every learning needs a full knowledge note. Some are tiny:

  • "This project uses tabs, not spaces"
  • "Always run pnpm not npm here"
  • "The API returns dates as Unix timestamps, not ISO"

These are instincts — atomic rules with confidence that grow stronger through reinforcement and decay through contradiction.

Quick Reference

CommandAction
/instinctsShow active instincts for current project
/instincts addManually add an instinct
/instincts reviewReview and adjust confidence of existing instincts
/instincts promotePromote high-confidence instincts to global learnings
/instincts pruneRemove low-confidence or stale instincts

Instinct Format

Each instinct is a single YAML entry:

- id: inst-20260310-a1b2c3
  rule: "Use pnpm instead of npm for this project"
  confidence: 0.7
  scope: project          # project | domain | universal
  category: tooling       # tooling | style | api | testing | architecture | convention
  created: 2026-03-10
  last_reinforced: 2026-03-10
  reinforcement_count: 1
  source: "User corrected npm to pnpm"
  tags: [pnpm, npm, package-manager]

Storage

Project-Scoped Instincts

Stored in .agents/instincts.yaml at the project root:

# .agents/instincts.yaml
# Auto-managed by /instincts skill. Edit manually if needed.
version: 1
instincts:
  - id: inst-20260310-a1b2c3
    rule: "Use pnpm instead of npm"
    confidence: 0.7
    scope: project
    category: tooling
    created: 2026-03-10
    last_reinforced: 2026-03-10
    reinforcement_count: 1
    source: "User corrected npm to pnpm"
    tags: [pnpm, npm]

Universal Instincts (Global Knowledge Base)

When an instinct reaches high confidence (>=0.8) and universal scope, promote it to the reflect-kb knowledge base via the reflect CLI:

# Promote instinct to a full learning note
if command -v reflect >/dev/null 2>&1; then
    reflect add docs/solutions/instincts/{instinct-id}.md \
        --entities docs/solutions/instincts/{instinct-id}.entities.yaml
elif [[ -x "$HOME/.local/bin/reflect" ]]; then
    "$HOME/.local/bin/reflect" add docs/solutions/instincts/{instinct-id}.md \
        --entities docs/solutions/instincts/{instinct-id}.entities.yaml
fi

Confidence Scoring

Scale

ConfidenceMeaningSource
0.3Weak signalSingle observation, no explicit confirmation
0.5ModerateConfirmed once or observed multiple times
0.7StrongExplicitly stated by user or confirmed 3+ times
0.9CertainRepeatedly reinforced, never contradicted

Confidence Dynamics

Reinforcement: confidence = min(0.9, confidence + 0.1)
Contradiction: confidence = max(0.0, confidence - 0.3)
Decay: confidence = max(0.0, confidence - 0.05) per 30 days inactive

Thresholds:

  • < 0.3 — Auto-prune (too weak to keep)
  • 0.3 - 0.5 — Low confidence, apply cautiously
  • 0.5 - 0.7 — Moderate confidence, apply by default
  • >= 0.8 — High confidence, candidate for promotion to global

Contradiction Handling

When a new observation contradicts an existing instinct:

  1. Reduce confidence of existing instinct by 0.3
  2. Create competing instinct with confidence 0.5
  3. If existing drops below 0.3, auto-prune it
  4. If both survive, flag for user review at next /instincts review

Workflow

Capturing Instincts (During Session)

Instincts are captured from:

  1. Explicit corrections: "No, use tabs here" -> instinct about indentation
  2. Approved patterns: User accepts a specific approach -> instinct about preference
  3. Repeated observations: Same tool/command used 3+ times -> instinct about convention
  4. /reflect output: Low-confidence signals from reflect that don't warrant full notes

Step 1: Detect Signal

During conversation, watch for:

  • Corrections to assumptions about project conventions
  • Explicit preferences ("always", "never", "prefer", "use X not Y")
  • Patterns that repeat across the session

Step 2: Check for Existing Instinct

# Check if we already have an instinct for this topic
grep -i "{keyword}" .agents/instincts.yaml 2>/dev/null
  • If match found: reinforce (bump confidence by 0.1)
  • If contradicts: handle contradiction (see above)
  • If new: create with initial confidence

Step 3: Set Initial Confidence

Signal SourceInitial Confidence
Explicit user correction ("always do X")0.7
User approval of approach0.5
Repeated observation (3+ times)0.5
Single observation0.3
From /reflect low-confidence signal0.3

Step 4: Write Instinct

Append to .agents/instincts.yaml. Create the file if it doesn't exist.

Step 5: Apply Instincts (Session Start)

At session start, load active instincts:

  1. Read .agents/instincts.yaml
  2. Filter to confidence >= 0.3
  3. Apply as soft rules (not hard requirements)
  4. Higher confidence = stronger adherence

Promotion to Global Learnings

When running /instincts promote:

  1. Filter instincts with confidence >= 0.8 and scope = universal
  2. For each candidate: a. Generate a learning note (using reflect learning_template.md format) b. Generate entity sidecar (.entities.yaml) c. Save to docs/solutions/instincts/{id}.md d. Index via learnings add
  3. Mark instinct as promoted: true (don't delete — keep for local quick reference)

Pruning

When running /instincts prune:

  1. Remove instincts with confidence < 0.3
  2. Decay instincts inactive for 30+ days
  3. Show remaining instincts sorted by confidence
  4. Allow user to manually remove any

Integration

With /reflect

  • /reflect captures HIGH/MEDIUM signals as full learnings
  • LOW signals route to instincts instead of being discarded
  • This ensures nothing is lost, even weak signals

With Session Start

  • Load .agents/instincts.yaml at session start
  • Apply as soft context for the session

With .agents/MEMORY.md

  • Instincts are complementary to MEMORY.md
  • MEMORY.md: free-form project notes (architecture, decisions)
  • Instincts: structured rules with confidence tracking
  • Instincts that stabilize at high confidence can be "hardened" into MEMORY.md entries

When not to use it

  • When a learning requires a full knowledge note instead of a micro-learning.
  • When the information is not a behavioral pattern or project-specific convention.

Limitations

  • Instincts are stored as lightweight YAML entries.
  • Universal instincts require the reflect CLI for promotion.
  • Confidence scores are between 0.3 and 0.9.

How it compares

This skill automatically captures and manages small, context-specific rules with confidence scores, unlike manually tracking such patterns.

Compared to similar skills

instincts side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
instincts (this skill)01moReviewIntermediate
notion-knowledge-capture109moNo flagsIntermediate
apple-reminders252moReviewBeginner
memory-keeper-proactive-context-maintenance69moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

notion-knowledge-capture

makenotion

Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.

10115

apple-reminders

openclaw

Manage Apple Reminders via the `remindctl` CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.

2593

memory-keeper-proactive-context-maintenance

b4CU-R4U

Automatically detect and maintain memory freshness by monitoring context staleness, significant code changes, task completions, and phase transitions. Proactively suggests and executes memory sync operations with user confirmation. Use when the user says "sync memory", "update context", or when the Skill detects that context is stale (>2 hours), significant changes have occurred (new commits), tasks completed, or major milestones reached. Replaces passive "context is stale" warnings with active maintenance.

694

notion-meeting-intelligence

openai

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

656

agent-memory

yamadashy

Use this skill when the user asks to save, remember, recall, or organize memories. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check your notes', 'clean up memories'. Also use proactively when discovering valuable findings worth preserving.

943

apple-notes

openclaw

Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.

718

Search skills

Search the agent skills registry