Skip to content
Agentmart
Submit a tool
This entry duplicates attic-fail, which is the one we list in search.

attic-fail

Record an approach that was tried and did not work, so nobody repeats it.

Skill by NishikantaRay

IndexedMIT★ 5
Write a review

Chalk Labs

Need help deploying attic-fail?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/nishikantaray-attic-fail-1e3a64

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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.

Use cases: productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions: not checked yet.

What's inside

Skill 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.
License
MIT
Allowed tools
Bash(node, "${CLAUDE_SKILL_DIR}/../attic/scripts/attic.js", *), Bash(node, "${CLAUDE_SKILL_DIR}/../attic/scripts/attic.js"*)
Instructions
63 lines in SKILL.md · view on GitHub

Before installing

  • Pre-approves some shell commands

Files (1)

  • SKILL.md

SKILL.md (first lines)

# 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> ``

From NishikantaRay/Attic, MIT.

More from NishikantaRay/Attic

Signals

Stars
5
Forks
0
Open issues
0
Last commit (this folder)
Sep 23, 2026 (1 month ago)
Last release
Sep 23, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

More from NishikantaRay

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get attic-fail running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying attic-fail?

CallGet help
Cite this page

attic-fail skill. Agent Mart. https://agentmart.dev/skills/nishikantaray-attic-fail-1e3a64 (last updated 2026-10-24)