Index of every page on this site: llms.txt
All skills
blader avatar

/napkin

@27fa60a
by Siqi Chenblader/napkin650 stars
55
Run it yourself

Maintain a per-repo napkin as a continuously curated runbook (not a session log). Activates EVERY session. Read and curate it before work, keep only recurring high-value guidance, organize by priority-sorted categories, and cap each category at top 10 items. The napkin lives at `.claude/napkin.md`.

Use this Skill: https://skilld.dev/gh/blader/napkin/napkin

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈77 tokens for metadata: the name and description. ≈698 when used: this file. ≈474 more on demand in 1 file.

Description uses 3.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈308 characters, or 3.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Napkin

You maintain a per-repo markdown runbook, not a chronological log. The napkin must be continuously curated for fast reuse in future sessions.

This skill is always active. Every session. No trigger required.

Session Start: Read And Curate

First thing, every session — read .claude/napkin.md before doing anything else. Internalize what's there and apply it silently. Don't announce that you read it. Just apply what you know.

Every time you read it, curate it immediately:

  • Re-prioritize items by importance (highest first).
  • Merge duplicates and remove stale/low-signal notes.
  • Keep only recurring, high-frequency guidance.
  • Ensure each item contains an explicit "Do instead" action.
  • Enforce category caps (top 10 per category).

If no napkin exists yet, create one at .claude/napkin.md:

# Napkin Runbook

## Curation Rules
- Re-prioritize on every read.
- Keep recurring, high-value notes only.
- Max 10 items per category.
- Each item includes date + "Do instead".

## Execution & Validation (Highest Priority)
1. **[YYYY-MM-DD] Short rule**
   Do instead: concrete repeatable action.

## Shell & Command Reliability
1. **[YYYY-MM-DD] Short rule**
   Do instead: concrete repeatable action.

## Domain Behavior Guardrails
1. **[YYYY-MM-DD] Short rule**
   Do instead: concrete repeatable action.

## User Directives
1. **[YYYY-MM-DD] Directive**
   Do instead: exactly follow this preference.

Adapt categories to the repo, but keep category structure and priority ordering. Do not use raw journal-style entries.

Continuous Runbook Updates

Update during work whenever you learn something reusable.

What qualifies for inclusion:

  • Frequent gotchas or surprising behavior in this repo/toolchain.
  • User directives that affect repeated behavior.
  • Non-obvious tactics that repeatedly work.

What does not qualify:

  • One-off timeline notes.
  • Verbose postmortems without reusable action.
  • Pure mistake logs without "Do instead" guidance.

Entry format requirements:

  • Include date added ([YYYY-MM-DD]).
  • Include short rule title.
  • Include explicit Do instead: line.
  • Keep wording concise and action-oriented.

Category And Priority Policy

  • Organize notes by category.
  • Keep each category sorted by importance descending.
  • Re-evaluate category choice and priority whenever editing.
  • Maximum 10 items per category; if over 10, remove lowest-priority entries.
  • Prefer fewer high-signal items over broad coverage.

Practical Rule

Think of napkin as a live knowledge base for future execution speed and reliability, not a history file.

Example Entry

1. **[2026-02-21] `rg` fails on giant expanded path lists**
   Do instead: run `rg` on directory roots or iterate files via `while IFS= read -r`.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warnings9mo4 checks · Risk SAFE
  • Gen Agent Trust Hub9mo

    This skill implements a persistent learning mechanism by tracking mistakes and preferences in a local file. It is generally safe but introduces a surface for indirect prompt injection if an attacker modifies the memory file in a shared repository.

  • Socket9mo

    1 alert: gptAnomaly

  • Snyk9mo

    Risk: LOW · No issues

  • Runlayer9mo

    3/3 files flagged

Signed by skilld at 27fa60a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 9 months ago
author
Codex
version
6.0.0
date
2026-02-21

README badge

README badge for blader/napkin