Skip to content
Back to skills

Attic Fail

ASecurity

Record an approach that was tried and did not work, so nobody repeats it. Use when the user says "that didn't work", "this approach failed", "record this failure", "don't try this again", "note what we ruled out", or when an attempt in this session was abandoned for a reason worth keeping. Also use for a temporary workaround that should not be mistaken for a real fix.

  • 4 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 19, 2026
ai-agentsbashnode

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add NishikantaRay/Attic --skill attic-fail --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Attic Fail?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Attic Fail
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nishikantaray-attic-fail-attic/badge)](https://www.skillsdirectory.com/skills/nishikantaray-attic-fail-attic)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: attic-fail
description: >
  Record an approach that was tried and did not work, so nobody repeats it.
  Use when the user says "that didn't work", "this approach failed", "record
  this failure", "don't try this again", "note what we ruled out", or when an
  attempt in this session was abandoned for a reason worth keeping. Also use
  for a temporary workaround that should not be mistaken for a real fix.
argument-hint: "[title of the approach that failed]"
allowed-tools: Bash(node "${CLAUDE_SKILL_DIR}/../attic/scripts/attic.js" *) Bash(node "${CLAUDE_SKILL_DIR}/../attic/scripts/attic.js"*)
version: 1.6.1
license: MIT
---

# Record a failed approach

Argument: `$ARGUMENTS` (a title, or empty to use the last failed attempt).

A failed approach is worth more than it looks. The next session will consider
the same idea for the same reasons, and the record of why it did not work is
what stops the second attempt from costing what the first one did.

## What to capture

Four things, in this order. The third is the one that matters — an approach
recorded without its reason just reads as defeatism and gets re-tried anyway.

1. **What was tried** — concretely enough to recognise the idea again.
2. **What happened** — the actual failure, error text copied verbatim.
3. **Why it failed** — the underlying reason, not the symptom.
4. **What to do instead**, if known.

## Recording it

```bash
node "${CLAUDE_SKILL_DIR}/../attic/scripts/attic.js" stash \
  --slug <slug> --kind finding --type failed-approach \
  --title "<what was tried>" \
  --hook "<the approach, and the one-line reason it failed>" \
  --files "<files that show why>" \
  [--commands "<command that demonstrated the failure>"] \
  [--confidence verified] \
  --body-file <tmpfile>
```

`--type failed-approach` is what keeps it out of the way of active
architectural decisions: it is recorded knowledge about a dead end, not a
recommendation. Pass `--confidence verified` only if you actually saw it fail
in this session; an approach you believe would fail is `unverified`, and the
body should say which it was.

For a temporary fix that works but should not last, use
`--type workaround` instead. Workarounds are always surfaced by
`/attic-review`, because a workaround that quietly becomes permanent is its
own kind of failure.

## Body shape

```markdown
## Tried
Added authentication directly inside the route handler.

## Result
Some routes bypassed the handler entirely; `npm test` failed 3 auth tests.

## Why it failed
Auth must run before route registration, and the handler runs after it.

## Instead
Register the middleware in src/middleware/auth.ts before the route table.
```

## Reply

`` Recorded `attic:<slug>` · <one line on why it failed> ``

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.