agentleFS
Sign inStart free
tonydzitonydzi/second-brain-starter-kit/skills/declined/SKILL.md

declined

Skill6 starsChanged 2 months agoMITView on GitHub

Look up the registry of declined and deferred decisions, so the same idea is never re-pitched: what was rejected, why, and under what condition to revisit. Read-only, and can also run the detector for new rejections in recent sessions. Triggers: "/declined", "did we reject this before".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read declined-decisions.md (the hub path above).

    line 19
  2. Distinctive:

    If the operator asked about a SPECIFIC topic — grep the registry for it and show the matches (what was rejected · why · under what …

    line 21
  3. Distinctive:

    If the idea being pitched right now is ALREADY in the registry — warn the operator explicitly ("this was declined on <date>, reason X, …

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OBJECTIVE: Show the registry of declined/deferred decisions (what · why · revisit-if) BEFORE (re-)pitching an idea — the anti "step on the same rake twice" guard. READ-ONLY: it writes nothing into the registry (the nightly scan and the human do that).

CONTEXT:

  • The canonical registry (this hub): %USERPROFILE%\.claude\projects\<hub-project>\memory\declined-decisions.md (a copy exists in the laptop project — always read the hub one).
  • The nightly detector: $IMPORTS_ROOT/declined-scan/declined_scan.py (scheduled task "Declined-Decisions Nightly Scan", ~03:45) — it catches new refusals from fresh sessions and parks them on the AUTO-CAPTURED shelf.
  • The rule (cross-actor): rejected or deferred a proposal → record it in the registry. The canon for human assistants lives in the Bible as the "record a rejected decision" rule.

STEPS:

  1. Read declined-decisions.md (the hub path above). 1b. Dead-man check on the watchdog (added 2026-07-04; catches the class "the task was silently disabled", as happened 06-22→06-27): read $IMPORTS_ROOT/declined-scan/highwater.json → if updated is older than 2 days the nightly watchdog is NOT running → check (Get-ScheduledTask -TaskName 'Declined-Decisions Nightly Scan').State, enable it (Enable-ScheduledTask), and report in one line. Fresh → move on silently.
  2. If the operator asked about a SPECIFIC topic — grep the registry for it and show the matches (what was rejected · why · under what condition to revisit).
  3. Otherwise — a short summary: how many entries, the most recent additions, and the AUTO-CAPTURED shelf (waiting for promotion).
  4. (Optional, on "run the scan") execute python $IMPORTS_ROOT/declined-scan/declined_scan.py and show the newly caught refusals.
  5. If the idea being pitched right now is ALREADY in the registry — warn the operator explicitly ("this was declined on <date>, reason X, revisit if Y") before going further.

OUTPUT: a short list of relevant refusals, or a registry summary. It writes NOTHING (except step 4, where the scan writes for itself). Finish the reply to a non-technical operator with an "In plain words" recap.

RELATION (do not duplicate): the source registry = memory [[declined-decisions]]; the nightly scan = declined_scan.py; the rule for humans = the Bible entry on recording rejected decisions.

<!--kit-footer-->

Like this skill? It is one of 100 in second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.

Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).

Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_

Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free