F Card
Create a single Logbook knowledge card from conversation context. Lightweight, no job required. Use when the user runs /f-card, says "capture this", "save this learning", "make a card for that", or when something just learned is worth persisting. One card from this conversation: not bulk extraction from completed jobs (f-catchup), and not promoting knowledge into the constitution (f-distill).
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use F Card when an AI agent needs a reusable SKILL.md workflow for this job: Create a single Logbook knowledge card from conversation context. Lightweight, no job required. Use when the user runs /f-card, says "capture this", "save this learning", "make a card for that", or when something just learned is worth persisting. One card from this conversation: not bulk extraction from completed jobs (f-catchup), and not promoting knowledge into the constitution (f-distill).
When not to use it
Skip F Card when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/f-card # Save SKILL.md to ~/.claude/skills/f-card/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/f-card/SKILL.md. For a shared project, commit the folder at .claude/skills/f-card/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the F Card skill for this task: Use F Card when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
68/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 52/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Topping Out: Logbook quick card
Create a single knowledge card from conversation context. Lightweight, no job required.
---
## Usage
``` /f-card <type> <description> ```
**Examples:**
- `/f-card insight a re-aimed GREEN mutation probe hides a missing test` - `/f-card method validated blueprint then execute` - `/f-card build rate limiter for the login endpoint`
**Type:** `insight` | `method` | `build` (case-insensitive; `project` is accepted as an old alias and written as BUILD)
One card per invocation. Run again for additional cards.
---
## Instructions
You create a single Logbook knowledge card from the current conversation context. No session file needed. Fast and focused.
### Step 1: Parse Arguments
Extract `type` (first word) and `description` (rest of the line).
If no arguments provided, analyze the conversation and suggest up to 3 candidates:
``` What should I capture? I see these candidates in our conversation:
1. [INSIGHT] [description of something learned] 2. [METHOD] [description of a reusable approach]
Pick one (run /f-card again for additional cards). ```
### Step 2: Read Template
Read the matching template:
- INSIGHT → `foreman/logbook/entries/insights/INSIGHT-TEMPLATE.md` - METHOD → `foreman/logbook/entries/methods/METHOD-TEMPLATE.md` - BUILD → `foreman/logbook/entries/builds/BUILD-TEMPLATE.md`
### Step 3: Check for Duplicates
Extract 2-3 distinctive keywords from the description. Grep each in `foreman/logbook/entries/`, **excluding `*TEMPLATE*`** (the templates contain every field name and example cluster):
``` Grep "keyword1" in foreman/logbook/entries/ (files_with_matches, glob "!*TEMPLATE*") Grep "keyword2" in foreman/logbook/entries/ (files_with_matches, glob "!*TEMPLATE*") ```
Check the first 5 results. If any match >80% of the card concept, warn:
``` Possible duplicate: INSIGHT_20260121_SIMILAR_NAME - Read existing card to confirm overlap - If confirmed: "This overlaps with [ID]. Add evidence to existing card instead? (y/n)" - If not: proceed with new card ```
### Step 4: Generate Card ID
``` TYPE_YYYYMMDD_SHORT_NAME ```
- Date = today - SHORT_NAME = 2-4 words from description, UPPER_SNAKE_CASE - Examples: `INSIGHT_20260220_REAIMED_PROBE_HIDES_GAP`, `METHOD_20260220_BLUEPRINT_THEN_EXECUTE`
### Step 5: Generate Card Content
From the conversation context, fill in the template sections.
**For INSIGHT cards:**
- Overview, Impact (severity + evidence), Pattern Structure, Anti-Pattern, Evidence instances, Applications - A **ruled-out** card (tag `ruled-out`, title "Ruled out: <option>"): a deliberate "no" on an option that could plausibly come back. It **must** fill the template's **Ruled out** section (**Why**, **Revisit if**). Other cards leave that section out, and the quality gate doesn't count it. Don't write one for an option nobody would propose again - Set `confidence` based on evidence strength: 1 instance = 75%, 2+ instances = 85%, quantified = 95%
**For METHOD cards:**
- Overview, Impact (severity + evidence), Steps, Before/After Example, When to Use - Set `success_rate` based on evidence: used once successfully = 100%, theoretical = 80%
**For BUILD cards:**
- Goal, Accomplished, Key Decisions, Methods Applied, Insights Discovered, Lessons Learned - Set `scope`: MAJOR (8+h), SIGNIFICANT (4-8h), MODERATE (2-4h), MINOR (<2h)
**Frontmatter for all cards:**
- `cluster`: the repo's own list. Clusters **emerge from this repo's cards**: read the `## Clusters` section of `logbook_index.md` and the `cluster:` lines of existing cards, and reuse a slug already in use when the card fits it. A new Logbook starts from a few generic starter clusters:
| Cluster | Topics | | ---------------------- | ----------------------------------------------- | | `development-workflow` | Reviews, work orders, gates, iteration, tooling | | `testing` | Tests, probes, fixtures, flaky or slow suites | | `security` | Auth, secrets, vulnerabilities, permissions | | `architecture` | Module boundaries, data model, interfaces |
Add a new slug (lowercase, hyphenated, named after the product area, e.g. `billing`, `search-index`, `db-migrations`) only when no existing one fits, and list it under `## Clusters` in `logbook_index.md` in the same pass as the card. When checking duplicates, search near-synonym slugs already in the corpus too (and array-valued clusters) rather than forcing a bad fit or minting a duplicate.
- `tags`: 3-6 specific keywords - `impact`: CRITICAL (2-10x improvement) | HIGH (significant measurable) | MEDIUM (moderate) | LOW (minor) - `session`: Use `conversation-YYYY-MM-DD` if no session exists
### Step 6: Quality Gate
Before showing the card, verify:
| Check | Requirement | If fails | | ----------------------- | ------------------------------------ | ------------------------------------------------- | | All sections | Every template section has content | Fill from conversation or mark `[needs evidence]` | | Confidence/success_rate | ≥ 70% (INSIGHT/METHOD; BUILD: n/a) | Needs more evidence, warn user | | Concrete example | At least 1 specific instance | Add from conversation context | | Actionable | Clear "when to use" / "applications" | Clarify |
Score (a heuristic to catch thin cards, not a measurement; the checks above are what matter):
``` Base: 50 +20 all sections filled +15 evidence strength: INSIGHT `confidence` ≥ 80% · METHOD `success_rate` ≥ 80% · BUILD: Accomplished cites a PR, merge sha or commit +10 has concrete example +5 has counter-example (INSIGHT only) ```
Minimum to create: **75/100**. If below, show score and missing items, ask user whether to fix or force-create.
### Step 7: Show Card and Confirm
Display the full card content to the user **before writing**:
``` ## Card Preview: TYPE_YYYYMMDD_SHORT_NAME
[full card content]
--- Quality: 85/100 File: foreman/logbook/entries/{type}/TYPE_YYYYMMDD_SHORT_NAME.md
Create this card? (y/n) ```
Wait for confirmation. Do not write until approved.
### Step 8: Write Card File
After approval, save to:
``` foreman/logbook/entries/insights/INSIGHT_YYYYMMDD_NAME.md foreman/logbook/entries/methods/METHOD_YYYYMMDD_NAME.md foreman/logbook/entries/builds/BUILD_YYYYMMDD_NAME.md ```
Confirm:
``` Card created: TYPE_YYYYMMDD_SHORT_NAME File: foreman/logbook/entries/{type}/TYPE_YYYYMMDD_SHORT_NAME.md Cluster: [cluster] | Impact: [impact]
Run /f-distill to propose it for the constitution. ```
### Step 9: Update the index and links
A card isn't in the Logbook until the index lists it. In the same pass as the write:
1. Add a row to the right table in `foreman/logbook/logbook_index.md` (`| ID | Summary | Impact | Conf | Job |`; Conf is `confidence` or `success_rate`; Job is the card's `job:` or `none`), and bump that table's `(n)`. 2. **Recount from the files, never by adding one:** count `[A-Z]*_20*.md` under each of `entries/insights`, `entries/methods`, `entries/builds`, excluding `*TEMPLATE*`, and write `**Total Cards**: <sum> (<m> METHOD, <i> INSIGHT, <b> BUILD)` and `**Last Updated**`. 3. If the card names related cards (`related:`), add each edge to `foreman/logbook/logbook_links.md` (`| From | Type | To |`) and recount `**Total Links**` from the table rows.
If the live count is **greater than 250**, run `/f-archive` through to the end (its automatic mode, under its guards). **Except during a close:** when `/f-signoff` runs these steps (its Steps 2.4 and 3.2), don't start it; the close archives once, at the end of its Step 3.2a.
---
## What This Does NOT Do
- Promote the card into the constitution (run `/f-distill` for that) - Require or update a session file - Create multiple cards (run again for more)
Intentionally lightweight: one card, in the right folder, listed in the index.
Intended uses
- Use F Card when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.