error-memory
Track Project Error Lessons
Teams lose time when agents repeat the same project mistakes. This skill records concise error lessons in a shared project file.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "error-memory" from https://skillstore.io/skills/aceek-error-memory.md and its manifest at https://skillstore.io/api/skills/aceek-error-memory/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "error-memory". A test failed because I used the wrong import path.
Expected outcome:
Adds a technical lesson that names the mistaken import assumption and the rule for checking local module paths first.
Using "error-memory". The user corrected a UI convention I missed.
Expected outcome:
Adds a context lesson describing the missed convention and the exact rule to apply before editing similar files.
Using "error-memory". I misunderstood the requested feature scope.
Expected outcome:
Adds a comprehension lesson that states the missed requirement and the rule for confirming scope before implementation.
Security Audit
Low RiskAll static command-execution findings are false positives caused by markdown inline code and code fences. The skill has one low-severity semantic concern because it instructs agents to create or append a project-local memory file.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (7)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/aceek-error-memory/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/aceek-error-memory?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/aceek-error-memory?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/aceek-error-memory/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/aceek-error-memory.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Aceek. (2026). error-memory security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/aceek-error-memory/audits/9BibTeX citation
@techreport{aceek-aceek-error-memory-2026,
author = {Aceek},
title = {error-memory security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/aceek-error-memory/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "error-memory security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "Aceek"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/aceek-error-memory/audits/9"
identifiers:
- type: other
value: "skillstore:aceek-error-memory:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prevent Repeated Build Mistakes
Record a failed build, its root cause, and the rule that prevents the same error later.
Capture Project Conventions
Document missed naming, structure, or framework conventions after a correction from a user.
Review Correction History
Scan past mistakes before assigning similar work or reviewing repeated agent behavior.
Try These Prompts
Use error-memory to record the mistake I just made, the root cause, and the rule I should follow next time.
Classify this failure with error-memory, then write a short lesson that prevents the same issue in this project.
Use error-memory to convert this user correction into a reusable project rule with a clear cause and fix.
Review the recent error-memory entries, identify repeated root causes, and propose three rules to reduce future failures.
Best Practices
- Confirm that the recorded lesson does not include secrets or private customer data.
- Keep each error entry short enough to scan before new work.
- Review existing entries before changing tests, build files, or established patterns.
Avoid
- Do not record blame, excuses, or long incident narratives.
- Do not write sensitive project details into shared memory files.
- Do not let old lessons override newer user instructions or repository policy.