Agent skill

Instinct System

by Resgrid in Resgrid/Core

Confidence-scored instinct system for learning project-specific patterns through an observe-hypothesize-confirm cycle.

Apache-2.0Auto-check passed

Install Instinct System

skills CLI
$ npx skills add Resgrid/Core --skill instinct-system -a claude-code

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

GitHub CLI
$ gh skill install Resgrid/Core instinct-system --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/Resgrid/Core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.forge/skills/instinct-system .claude/skills/instinct-system && 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
instinct-system
GitHub stars
229
Token cost
~2.8k tokens
SKILL.md length
612 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
Apache-2.0

At a glance

Confidence-scored instinct system for learning project-specific patterns through an observe-hypothesize-confirm cycle.

  • Works in 5 steps: Instincts are hypotheses, not rules — An… → Confidence scoring drives behavior… → Project-scoped, never global — Instincts… → …
  • SKILL.md covers Core Principles, Patterns, Anti-patterns and Decision Guide
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Instinct System is an agent skill from Resgrid/Core. Confidence-scored instinct system for learning project-specific patterns through an observe-hypothesize-confirm cycle. Instincts start as low-confidence hypotheses and graduate to permanent rules in MEMORY.md once confirmed. Stored per-project in .claude/instincts.md. Load this skill when you notice a recurring pattern, want to track a project convention, encounter "learn this", "I think they always", "notice a pattern", "instinct", "hypothesis", "confidence", or when starting a session (to load existing…

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

The repository describes itself as: The Open Source Computer Aided Dispatch (CAD), Personnel, Shift Management, Automatic Vehicle Location (AVL) and Emergency Management Platform that powers Resgrid.com. The licence is Apache-2.0.

Example prompts

  • “learn this”
  • “I think they always”
  • “notice a pattern”
  • “/instinct-system”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Instincts are hypotheses, not rules — An instinct starts as a guess based on a single observation. It has no authority until confirmed…
  2. Confidence scoring drives behavior (0.3-0.9) — Each instinct carries a numeric confidence that determines how Claude acts on it. At 0.3…
  3. Project-scoped, never global — Instincts are stored per-project in .claude/instincts.md. What holds true in one codebase may be wrong in…
  4. Observe-Hypothesize-Confirm cycle — The lifecycle is disciplined: see a pattern, form a hypothesis, actively seek confirming or…
  5. Evolution path to permanence — Instincts are temporary by design. At 0.9 confidence, they graduate to MEMORY.md as permanent rules or…

What it can do on your machine

Read from SKILL.md and the folder at commit a31015f. 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 markdown).

    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

Instinct System loads about 2.8k tokens when it runs. Until then it costs about 134 tokens; SKILL.md has 612 words of instructions outside code blocks.

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

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 Resgrid/Core at commit a31015f, republished under its Apache-2.0 licence (© Resgrid). 612 words, ~2,818 tokens.

Download SKILL.mdSave it as .claude/skills/instinct-system/SKILL.md (or your agent's skills folder).
name
instinct-system
description
Confidence-scored instinct system for learning project-specific patterns through an observe-hypothesize-confirm cycle. Instincts start as low-confidence hypotheses and graduate to permanent rules in MEMORY.md once confirmed. Stored per-project in .claude/instincts.md. Load this skill when you notice a recurring pattern, want to track a project convention, encounter "learn this", "I think they always", "notice a pattern", "instinct", "hypothesis", "confidence", or when starting a session (to load existing instincts).

Instinct System

Core Principles

  1. Instincts are hypotheses, not rules — An instinct starts as a guess based on a single observation. It has no authority until confirmed across multiple instances. Never treat a first observation as a project convention. "I saw one handler use sealed " is an instinct at 0.3; "all 12 handlers use sealed" is a rule at 0.9.

  2. Confidence scoring drives behavior (0.3-0.9) — Each instinct carries a numeric confidence that determines how Claude acts on it. At 0.3, merely note it. At 0.5, mention it when relevant. At 0.7, follow it by default. At 0.9, promote it to a permanent rule. Never apply a low-confidence instinct without flagging the uncertainty.

  3. Project-scoped, never global — Instincts are stored per-project in .claude/instincts.md. What holds true in one codebase may be wrong in another. A project using internal sealed class everywhere says nothing about a different project that uses public class with interface testing. Instincts do not transfer at full confidence.

  4. Observe-Hypothesize-Confirm cycle — The lifecycle is disciplined: see a pattern, form a hypothesis, actively seek confirming or disconfirming evidence, adjust confidence accordingly. Passive observation is not enough. When you form an instinct, look for it in the next 2-3 related files.

  5. Evolution path to permanence — Instincts are temporary by design. At 0.9 confidence, they graduate to MEMORY.md as permanent rules or trigger updates to relevant skills. An instinct that never reaches 0.7 after 5+ observations should be discarded, not left to rot.

Patterns

Instinct Lifecycle

The full lifecycle from first observation to permanent rule:

1. OBSERVE
   During normal work, notice something that might be a pattern.
   "This handler is internal sealed class. Is that the convention?"

2. HYPOTHESIZE
   Create an instinct with initial confidence 0.3.
   Write to .claude/instincts.md:
   - Use `sealed` on all handler classes | confidence: 0.3 | seen: 1 | last: 2025-07-15

3. SEEK CONFIRMATION
   When working in related areas, actively check for the pattern.
   Open 2-3 other handlers. Do they all use `internal sealed class`?

4. CONFIRM or DISCONFIRM
   - If confirmed: increment `seen`, raise confidence per the adjustment rules
   - If contradicted: halve confidence, note the exception
   - If mixed: hold confidence steady, note the split

5. PROMOTE
   At 0.9, present to the user for promotion to MEMORY.md.
   "I've observed [pattern] across [N] instances. Should I add this
   as a permanent rule to MEMORY.md?"
Instinct Storage Format

Store instincts in .claude/instincts.md with categories and structured metadata:

markdown
# Project Instincts

## Code Style [0.7]
- Use `sealed` on all handler classes | confidence: 0.8 | seen: 5 | last: 2025-07-15
- Prefix private fields with underscore | confidence: 0.5 | seen: 2 | last: 2025-07-14

## Architecture [0.6]
- Feature folders use singular names (Order, not Orders) | confidence: 0.7 | seen: 4 | last: 2025-07-15

## Naming [0.5]
- Command classes end in Command, not Request | confidence: 0.5 | seen: 3 | last: 2025-07-15

Category header [0.7] = average confidence. Use standard categories: Code Style, Architecture, Naming, Testing, Data Access, API Design, Configuration, Performance, Tooling. Each entry: description | confidence: N | seen: N | last: date.

Confidence Adjustment Rules

Follow these rules precisely. No ad-hoc scoring.

CONFIRMATION TRACK:
  First observation         → 0.3   (hypothesis formed)
  Second confirmation       → 0.5   (pattern emerging)
  Third confirmation        → 0.7   (likely convention)
  Fourth+ confirmation      → 0.8   (strong convention)
  Fifth+ with zero contradictions → 0.9 (promotion candidate)

CONTRADICTION HANDLING:
  Any contradiction          → halve current confidence
  Example: instinct at 0.7, contradicted → drops to 0.35
  Two contradictions in a row → drop to 0.1 (effectively dead)

USER OVERRIDE:
  User explicitly confirms   → jump to 0.8
  User explicitly corrects   → drop to 0.0 (remove the instinct)
  User says "sometimes"      → cap at 0.5 (conditional pattern)

STALENESS:
  No new observations for 10+ sessions → flag for review
  Contradicted and not re-confirmed for 5 sessions → remove
Acting on Instincts by Confidence Level
0.0 - 0.2  → IGNORE — insufficient evidence, do not mention
0.3 - 0.4  → NOTE — record internally, do not apply
0.5 - 0.6  → MENTION — "I notice this project may use [pattern]. Should I follow it?"
0.7 - 0.8  → FOLLOW — apply by default, mention when first applied
0.9        → PROMOTE — offer to add to MEMORY.md as a permanent rule

When generating code, apply instincts at 0.7+ silently. For instincts at 0.5-0.6, mention them as suggestions. Never silently apply an instinct below 0.7.

Seeking Confirmation Actively

Do not wait passively for evidence. When you form a new instinct, look for it:

ACTIVE SEEKING PROTOCOL:
1. Form instinct: "This project uses Result<T> for handler returns"
2. Before next code generation, check 2-3 existing handlers:
   → Use find_symbol to locate other handlers
   → Use get_public_api to check their return types
3. Count matches and mismatches
4. Adjust confidence based on findings
5. Update .claude/instincts.md with new count and confidence

EXAMPLE:
  New instinct: "Handlers return Result<T>" at 0.3
  → Check CreateOrderHandler: returns Result<OrderResponse> ✓
  → Check GetProductHandler: returns Result<ProductResponse> ✓
  → Check DeleteUserHandler: returns Task<IResult> ✗
  Result: 2/3 match → raise to 0.5, note the exception
  Updated: Handlers return Result<T> | confidence: 0.5 | seen: 3 | last: 2025-07-15
           Exception: DeleteUserHandler uses Task<IResult>
Promotion Protocol

When an instinct reaches 0.9 confidence:

PROMOTION STEPS:
1. Present the evidence to the user:
   "I've observed [pattern] across [N] instances with zero contradictions:
    - CreateOrderHandler: ✓
    - UpdateOrderHandler: ✓
    - DeleteOrderHandler: ✓
    - GetProductHandler: ✓
    - CreateProductHandler: ✓
    Should I add this as a permanent rule to MEMORY.md?"

2. If user approves:
   - Add to MEMORY.md under the appropriate category
   - Remove from .claude/instincts.md
   - Format as a clear, generalized rule (use self-correction-loop generalization)

3. If user declines:
   - Cap confidence at 0.8
   - Note: "User reviewed, chose not to promote"
   - Keep in instincts for continued reference

4. If user provides context:
   - "That's only for command handlers, not query handlers"
   - Adjust the instinct to be more specific
   - Reset confidence to 0.5 (narrowed scope needs re-confirmation)
Show full SKILL.md (250 more words)Show less
Export and Import Between Projects

Export instincts at 0.7+ to .claude/instincts-export.md. On import, apply 0.2 confidence decay (0.9 becomes 0.7, 0.7 becomes 0.5). Never import above 0.7 — every project must confirm locally. Mark imported instincts with source: "imported from [project]".

Session-Start Instinct Loading

At the beginning of each session, load and apply instincts:

SESSION START:
1. Read .claude/instincts.md (if it exists)
2. Load all instincts at 0.7+ into active context
3. Note instincts at 0.5-0.6 for mention-when-relevant
4. Ignore instincts below 0.5 (they'll be confirmed or discarded organically)
5. Check for stale instincts (no updates in 10+ sessions) — flag for review

Anti-patterns

Over-Eager Pattern Recognition
# BAD — treating first observation as a rule
*Reads one handler file*
"This project always uses internal sealed class on handlers."
*Generates 5 new handlers with internal sealed — but the project
 actually uses public class in 8 out of 9 existing handlers*

# GOOD — forming a hypothesis and seeking confirmation
*Reads one handler file*
"Noticed CreateOrderHandler uses internal sealed class.
 Forming instinct at 0.3. Let me check a few more handlers..."
*Checks 3 more handlers, finds they all use public class*
"Disconfirmed. The one internal sealed handler was an exception."
Stagnant Instincts
# BAD — instincts sit at 0.3 forever, never confirmed or discarded
.claude/instincts.md has 40 instincts, 35 of them at confidence 0.3
from 3 months ago — useless noise

# GOOD — actively seek confirmation or discard
After forming an instinct, check 2-3 related files in the same session.
Instincts that can't reach 0.5 within 3 sessions get removed.
Global Instincts
# BAD — applying instincts from one project to another at full confidence
"ProjectA uses FluentValidation, so ProjectB must too."
*ProjectB uses DataAnnotations exclusively*

# GOOD — project-scoped instincts with import decay
"ProjectA used FluentValidation (0.9). Importing to ProjectB at 0.7.
 Let me check what ProjectB actually uses..."
*Finds DataAnnotations → drops to 0.0, removes the instinct*
Instinct Hoarding
# BAD — never cleaning up the instinct file
.claude/instincts.md grows to 200 lines, full of contradictions
and instincts that were never confirmed

# GOOD — periodic cleanup
Every 5 sessions, scan instincts:
- Remove anything below 0.2
- Remove anything stale (no update in 10+ sessions)
- Promote anything at 0.9+
- Keep the file under 50 active instincts

Decision Guide

ScenarioAction
First time seeing a patternCreate instinct at 0.3, seek confirmation in 2-3 related files
Pattern seen twiceRaise to 0.5, keep seeking
Pattern seen 3+ times with no contradictionsRaise to 0.7, start following by default
Pattern contradictedHalve confidence, note the exception
User says "we always do X"Create instinct at 0.8 (user confirmation)
User says "no, that's wrong"Drop instinct to 0.0, remove it
Instinct at 0.9Present evidence to user, offer promotion to MEMORY.md
Instinct stale for 10+ sessionsFlag for review, ask user if it's still valid
Starting a new projectDo not import instincts from other projects above 0.7
Similar project, want to share instinctsExport at 0.7+, import with 0.2 decay
Instinct file exceeds 50 entriesAudit: remove dead instincts, promote mature ones
Generating code and instinct is 0.5-0.6Mention the instinct, ask before applying
Generating code and instinct is 0.7+Apply silently, mention on first use
Conflicting instincts in same categoryKeep both, note the conflict, seek the distinguishing condition
User partially confirms ("only for commands")Narrow scope, reset to 0.5, re-confirm with narrowed definition

© Resgrid, Apache-2.0. 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 .forge/skills/instinct-system of Resgrid/Core.

Open the folder on GitHubat commit a31015f

Compare with similar skills

Instinct System 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.

Instinct System compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Instinct System this skillResgrid/Core229—~2.8kAutomated safety check: PassApache-2.0
Harness Scoreruvnet/ruflo74k—~605Automated safety check: NotesMIT
Score Evalsickn33/agentic-awesome-skills47k1 repos~304Automated safety check: PassMIT
UI Scoresickn33/agentic-awesome-skills47k1 repos~1.8kAutomated safety check: PassMIT
Omh Instinct Ledgerrlaope/oh-my-hermes3.2k—~1.8kAutomated safety check: PassMIT
Release Note Editorial Scoringdotnet/core22k—~1.8kAutomated safety check: PassMIT

Similar skills

  • Harness Score

    ruvnet/ruflo

    5-dimension harness readiness scorecard from metaharness score <path.

    74k GitHub stars~605 tokensUpdated today
    DevelopmentAuto-check: notes
  • Score Eval

    sickn33/agentic-awesome-skills

    Imported skill score-eval from upstream source. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 1 repo~304 tokens
    EducationAuto-check passed
  • UI Score

    sickn33/agentic-awesome-skills

    Score a UI file's design quality 0-100 against StyleSeed's design language — per-category breakdown, the worst offenders, and a prioritized fix list.

    47k GitHub starsUsed in 1 repo~1.8k tokens
    Testing & QAAuto-check passed
  • Omh Instinct Ledger

    rlaope/oh-my-hermes

    [omh] Recurring lessons worth promoting: turn repeated project or cross-project lessons into atomic, confidence-scored instinct candidates with scoped promotion and export boundaries.

    3.2k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Official

    Scores candidate features by how much a developer upgrading would care, giving a shared rubric and cut guidance for release notes, blog posts and docs.

    22k GitHub stars~1.8k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Prioritizing Vulnerabilities With Cvss Scoring

    mukul975/Anthropic-Cybersecurity-Skills

    The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity.

    34k GitHub stars~1.9k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from Resgrid/Core

All 23 skills in this repo
  • 80 20 Review

    Resgrid/Core

    Focus code review effort on the 20% of code that causes 80% of issues.

    229 GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Autonomous Loops

    Resgrid/Core

    Autonomous iteration loops for .NET development: build-fix, test-fix, refactor, and scaffold loops.

    229 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Learning Log

    Resgrid/Core

    Auto-document insights and discoveries during development sessions.

    229 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Logging

    Resgrid/Core

    Observability for .NET 10 applications. An agent skill from Resgrid/Core.

    229 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Model Selection

    Resgrid/Core

    Strategic Codex model selection for .NET development workflows.

    229 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Model Selection

    Resgrid/Core

    Strategic Claude model selection for .NET development workflows.

    229 GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Instinct System

What does Instinct System do?

Confidence-scored instinct system for learning project-specific patterns through an observe-hypothesize-confirm cycle. Instinct System is an agent skill from Resgrid/Core. Confidence-scored instinct system for learning project-specific patterns through an observe-hypothesize-confirm cycle.

How do I install Instinct System in Claude Code?

Run `npx skills add Resgrid/Core --skill instinct-system -a claude-code`. Or copy the skill folder (.forge/skills/instinct-system in Resgrid/Core) into .claude/skills/instinct-system in your project. Claude Code loads it when a task matches its description.

How do I install Instinct System in Codex?

Run `npx skills add Resgrid/Core --skill instinct-system -a codex`. Or copy the skill folder (.forge/skills/instinct-system in Resgrid/Core) into .agents/skills/instinct-system in your project. Codex loads it when a task matches its description.

Can I use Instinct System 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 Resgrid/Core --skill instinct-system -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/instinct-system, .gemini/skills/instinct-system, .github/skills/instinct-system and .opencode/skills/instinct-system in your project.

What does Instinct System need to run?

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

Does Instinct System 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 Instinct System 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 Instinct System use?

Instinct System is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Instinct System use?

About 2.8k tokens (SKILL.md is roughly 11k 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 Instinct System?

Skills that share tags, products or a category with Instinct System: Harness Score (ruvnet/ruflo, 74k stars), Score Eval (sickn33/agentic-awesome-skills, 47k stars), UI Score (sickn33/agentic-awesome-skills, 47k stars) and Omh Instinct Ledger (rlaope/oh-my-hermes, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Instinct System?

Resgrid (a GitHub organization) maintains it in Resgrid/Core, which has 229 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 7, 2026.

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