agenticnotetaking/skills/goodjob
skills/goodjob/SKILL.md
--- tldr: Capture positive calibration with context category: utility --- # /eidos:goodjob Capture a moment of good AI output with context, so future sessions can calibrate on what works. ## Usage ``` /eidos:goodjob [description of what was good] ``` ## Instructions ### 1. Understand the Moment Identify what was good — could be: - A well-chosen framing or metaphor - A structural insight or distinction - Good taste in a design decision - An approach that clicked - Anything the human found
$ install --global
skillsauthnpx skillsauth add agenticnotetaking/eidos skills/goodjobInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 1, 2026, 6:26 AM59.4s2 files scanned
SKILL.md
- tldr:
- Capture positive calibration with context
- category:
- utility
/eidos:goodjob
Capture a moment of good AI output with context, so future sessions can calibrate on what works.
Usage
/eidos:goodjob [description of what was good]
Instructions
1. Understand the Moment
Identify what was good — could be:
- A well-chosen framing or metaphor
- A structural insight or distinction
- Good taste in a design decision
- An approach that clicked
- Anything the human found valuable
If the description is brief, look back in the conversation for the full context.
2. Draft the Record
Capture three things:
- What — the output or idea itself (quote or paraphrase)
- Context — what we were working on, what prompted it
- Why it worked — what made this good (the human's words or inferred from their reaction)
Format:
---
tldr: [brief description of what was good]
status: unprocessed
---
# Goodjob: [claim about what worked]
## What
[The output, idea, or moment — quoted or paraphrased]
## Context
[What we were working on, what question or task prompted this]
## Why It Worked
[What made this good — from the human's feedback or inferred]
# Goodjob: [next thing]
<!-- Just do this for all things in the session that worked well or got explicit postivive feedback from the human>
3. Present and Write
Show the draft to the user.
If approved, run date '+%y%m%d%H%M' to get the current timestamp and write to memory/goodjob - <timestamp> - <claim>.md (per [[spec - naming - prefixes structure filenames as prefix claim pairs]], e.g. goodjob - 2602141030 - well chosen auth framing.md).
Commit.
Processing
Goodjob files start as status: unprocessed.
/eidos:next surfaces unprocessed goodjobs.
To process: run /eidos:toeidos on the goodjob file to extract the pattern into a claim, rule, or spec update, then set status: processed.
Output
- Creates:
memory/goodjob - <timestamp> - <claim>.md - Status:
unprocessed→processed(after pattern is extracted via/eidos:toeidos)
Related Skills
agenticnotetaking/skills/outbox
development
VerifiedTrustedCommunity
--- tldr: Check the status of messages you sent to peer inboxes category: core --- # /eidos:outbox Find messages **you sent** to peer repos and report their status. Your sent messages live in the peers' inboxes, not here. So this skill sweeps every registered peer and reads back what became of them. This is the mirror of [[spec - inbox skill - read and act on your own inbox]]. - The inbox is messages others sent **to** you. You own and edit it. - The outbox is messages you sent **to** others.
53SKILL.mdUpdated Jun 9, 2026
agenticnotetaking/skills/message
development
VerifiedTrustedCommunity
--- tldr: Send a message to a peer repo's inbox category: core --- # /eidos:message Write a message into another repo's `agent-inbox/`. The recipient is a peer repo, addressed by its registered name. See [[spec - agent communication - cross repo inboxes with append only messages and registry resolution]]. ## Usage ``` /eidos:message [recipient repo] [what to say] ``` ## Instructions ### 1. Resolve the recipient - Identify the recipient repo name. Ask if not given. - Resolve its path: `
53SKILL.mdUpdated Jun 9, 2026
agenticnotetaking/skills/inbox
development
VerifiedTrustedCommunity
--- tldr: Read and act on your own inbox category: core --- # /eidos:inbox List and work through messages other repos have left in your `agent-inbox/`. You own this inbox. You may edit its files freely. Agents from other repos may push **new** messages into your inbox at any time. They never edit existing files. Only you do. So re-check the inbox. Don't assume it is unchanged since you last looked. See [[c - foreign agents append to an inbox - only the owner edits in place]]. See [[spec - ag
53SKILL.mdUpdated Jun 9, 2026
agenticnotetaking/skills/archive
tools
VerifiedTrustedCommunity
--- tldr: Move done files into archive subdirs (memory/ and agent-inbox/) category: utility --- # /eidos:archive Retire finished files into the `archive/` sibling of their directory. Done `memory/` files into `memory/archive/`, done inbox messages into `agent-inbox/archive/`. A `git mv`, never a rename. The basename is preserved, so wiki links keep resolving. See [[c - archiving moves done files into an archive subdir preserving basename and links]]. ## Usage ``` /eidos:archive [optional fil
53SKILL.mdUpdated Jun 9, 2026