← Back to the catalog 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
View on GitHub ↗ Copy repo URL Copy SKILL.md link /plugin marketplace add aiskillstore/marketplace The exact command may vary by repository. Check the README on GitHub.
For the skill author
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
Markdown HTML
[](https://www.skillteca.com.br/skills/error-memory?utm_source=badge&utm_medium=readme&utm_campaign=badge) Copy snippet Team Mode security research skill orchestrates 3 vulnerability hunters and 2 PoC engineers to audit a codebase in parallel, prove exploitability, classify root causes, and calibrate severity. It is used for security review, vulnerability research, exploitability audit, and threat model validation.
Segurança by code-yeongyu
Provide a comprehensive, structured reference for the 100 most critical web application vulnerabilities organized by category. This skill enables systematic vulnerability identification, impact assessment, and remediation guidance across the full spectrum of web security threats.
Segurança #github #git by sickn33
Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.
Segurança #github #git by sickn33
Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
Segurança #github #git by sickn33
Category alert
One short email with only the new Segurança skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
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
Identify error type
tech : build, tests, syntax, runtimectx : conventions, patterns, project stackcomp : misunderstood requirements
Analyze root cause (not symptom)
Formulate fix as reusable rule
Append line to .claude/errors.md:
| MM-DD | type | Short error | Root cause | Rule to follow |
Create file if missing with this template:
# 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
Read full description↓
Comments · No comments No comments yet. Be the first. 