smithery/aceek

error-memory

Use when: making a mistake, breaking build/tests, realizing wrong approach, misunderstanding requirements, using wrong patterns, forgetting conventions, receiving correction from user, unexpected behavior, or any error situation

Installation

$ npx skills add smithery/aceek --skill error-memory

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/aceek.

npx skills add smithery/aceek

Browse all from smithery/aceek

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,498 B
  • docs SUMMARY.md 248 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Error Memory

Document errors to avoid repeating them.

Trigger

Invoke when:

  • Build/tests fail after your action
  • User corrects you
  • You realize a wrong approach
  • You forget a project convention
  • Unexpected behavior occurs

Process

  1. Identify error type

- tech : build, tests, syntax, runtime - ctx : conventions, patterns, project stack - comp : misunderstood requirements

  1. Analyze root cause (not symptom)
  1. Formulate fix as reusable rule
  1. Append line to .claude/errors.md:

``markdown | MM-DD | type | Short error | Root cause | Rule to follow | ``

  1. Create file if missing with this template:

```markdown # Project Errors

> Past Claude mistakes on this project. Check before acting.

Date Type Error Cause Fix

## Legend - tech : Technical (build, tests, syntax) - ctx : Context (conventions, patterns) - comp : Comprehension (misunderstood request) ```

Rules

  • One line = one error (no paragraphs)
  • Fix = actionable rule, not excuse
  • Cause = why, not what
  • Keep < 100 lines (archive if needed)
  • Check errors.md before acting on any project