[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PFHZRDQE1QSZPQ1ZKEYVR5":3,"skill-same:01M6PFHZRDQE1QSZPQ1ZKEYVR5":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6PFHZRDQE1QSZPQ1ZKEYVR5","mistakes",null,"List past mistakes engram has learned in this project — failures, regressions, broken assumptions. Use before starting a non-trivial change to surface relevant prior failures, or when debugging to check if this issue has been seen before.","NickCirv\u002Fengram","NickCirv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F251763095?v=4","01M6PFHRC7084HAANFHTWMP46V","Nick Ashkar","01M6PFHRGMGAMXBHQCWQMV56DQ",143,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNickCirv\u002Fengram\u002Fblob\u002Fmain\u002Fplugins\u002Fanthropic-marketplace\u002Fengram\u002Fskills\u002Fmistakes\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30],"change","debugging","check","broken","list","use","issue","engram","project","learned","relevant","past","2026-11-10 10:12:30",false,"---\ndescription: List past mistakes engram has learned in this project — failures, regressions, broken assumptions. Use before starting a non-trivial change to surface relevant prior failures, or when debugging to check if this issue has been seen before.\n---\n\n# engram mistakes\n\nSurface bi-temporal mistake memory from engram's graph. Each mistake has a\n`valid_until` timestamp and an `invalidated_by_commit` reference, so an old\nmistake auto-expires when its underlying cause is fixed.\n\nRun:\n\n```\nengram mistakes -p $CLAUDE_PROJECT_DIR\n```\n\nThe output lists active (still-valid) mistakes with confidence scores. When\na mistake matches a query, engram surfaces it with ⚠️ at the top of the\ncontext packet, weighted 2.5× to ensure it gets attention.\n\nUse this skill:\n\n- Before refactoring a module: \"are there known sharp edges here?\"\n- During debugging: \"has this kind of error been seen before?\"\n- When onboarding to a new area of the codebase: \"what's broken or fragile?\"\n\nTo record a new mistake explicitly:\n\n```\nengram learn \"Don't pass options.scope=user; SETTINGS_LOCAL takes precedence.\" -p $CLAUDE_PROJECT_DIR\n```\n\n## Example invocations\n\n**User:** \"I'm about to refactor the rate limiter — anything I should know?\"\n**You:** Run `engram mistakes -p $CLAUDE_PROJECT_DIR`. Filter mentally for entries related to \"rate\", \"limit\", \"mutex\", or the file paths the user mentions. Surface the matches with their confidence scores: \"engram has 3 active mistakes near this code, and one of them flagged this exact module:\"\n\n**User:** \"Why does this test keep flaking?\"\n**You:** Run `engram mistakes -p $CLAUDE_PROJECT_DIR`. Look for entries about flakiness, timing, race conditions, or the test file's name. If a related mistake exists, quote it verbatim — chances are someone already debugged this.\n\n**User:** \"We just fixed a race condition in the queue worker. Remember it for next time.\"\n**You:** Run `engram learn \"Queue worker had a race condition: don't read state.queue inside the await; snapshot it first\" -p $CLAUDE_PROJECT_DIR`. Confirm to the user that the mistake is recorded and will surface with ⚠️ on future Edits to that file.\n\n**User:** \"Has anyone fixed this kind of bug before?\"\n**You:** Run `engram mistakes -p $CLAUDE_PROJECT_DIR`. The graph carries 2.5x relevance boost on matching results, so if a similar fix exists, it surfaces near the top.\n\n**User:** \"Clear the mistake list — we've outgrown those warnings\"\n**You:** Don't. Mistakes are bi-temporal — they auto-expire when their underlying cause is fixed (`invalidated_by_commit` set automatically). Manual clearing should be the last resort. If a specific mistake is no longer relevant but hasn't auto-expired, the user can edit `.engram\u002Fgraph.db` with sqlite3, but recommend living with one extra warning instead.\n\n## When NOT to fire this skill\n\n- The user is debugging a fresh problem with no engram-recorded history. The mistake list is for past failures, not unrelated current issues.\n- The graph is uninitialized. Recommend `engram init .` first.\n- The user wants to view *successful* patterns, not failures. Use `engram query` for those.\n","# engram mistakes\n\nSurface bi-temporal mistake memory from engram's graph. Each mistake has a\n`valid_until` timestamp and an `invalidated_by_commit` reference, so an old\nmistake auto-expires when its underlying cause is fixed.\n\nRun:\n\n```\nengram mistakes -p $CLAUDE_PROJECT_DIR\n```\n\nThe output lists active (still-valid) mistakes with confidence scores. When\na mistake matches a query, engram surfaces it with ⚠️ at the top of the\ncontext packet, weighted 2.5× to ensure it gets attention.\n\nUse this skill:\n\n- Before refactoring a module: \"are there known sharp edges here?\"\n- During debugging: \"has this kind of error been seen before?\"\n- When onboarding to a new area of the codebase: \"what's broken or fragile?\"\n\nTo record a new mistake explicitly:\n\n```\nengram learn \"Don't pass options.scope=user; SETTINGS_LOCAL takes precedence.\" -p $CLAUDE_PROJECT_DIR\n```\n\n## Example invocations\n\n**User:** \"I'm about to refactor the rate limiter — anything I should know?\"\n**You:** Run `engram mistakes -p $CLAUDE_PROJECT_DIR`. Filter mentally for entries related to \"rate\", \"limit\", \"mutex\", or the file paths the user mentions. Surface the matches with their confidence scores: \"engram has 3 active mistakes near this code, and one of them flagged this exact module:\"\n\n**User:** \"Why does this test keep flaking?\"\n**You:** Run `engram mistakes -p $CLAUDE_PROJECT_DIR`. Look for entries about flakiness, timing, race conditions, or the test file's name. If a related mistake exists, quote it verbatim — chances are someone already debugged this.\n\n**User:** \"We just fixed a race condition in the queue worker. Remember it for next time.\"\n**You:** Run `engram learn \"Queue worker had a race condition: don't read state.queue inside the await; snapshot it first\" -p $CLAUDE_PROJECT_DIR`. Confirm to the user that the mistake is recorded and will surface with ⚠️ on future Edits to that file.\n\n**User:** \"Has anyone fixed this kind of bug before?\"\n**You:** Run `engram mistakes -p $CLAUDE_PROJECT_DIR`. The graph carries 2.5x relevance boost on matching results, so if a similar fix exists, it surfaces near the top.\n\n**User:** \"Clear the mistake list — we've outgrown those warnings\"\n**You:** Don't. Mistakes are bi-temporal — they auto-expire when their underlying cause is fixed (`invalidated_by_commit` set automatically). Manual clearing should be the last resort. If a specific mistake is no longer relevant but hasn't auto-expired, the user can edit `.engram\u002Fgraph.db` with sqlite3, but recommend living with one extra warning instead.\n\n## When NOT to fire this skill\n\n- The user is debugging a fresh problem with no engram-recorded history. The mistake list is for past failures, not unrelated current issues.\n- The graph is uninitialized. Recommend `engram init .` first.\n- The user wants to view *successful* patterns, not failures. Use `engram query` for those.\n",{"description":7},"main","df445d3132583100e6d5106af4b4c91c01a2ba15","plugins\u002Fanthropic-marketplace\u002Fengram\u002Fskills\u002Fmistakes",15,"https:\u002F\u002Fgithub.com\u002FNickCirv\u002Fengram","https:\u002F\u002Fgithub.com\u002FNickCirv","https:\u002F\u002Fcirvgreen.com","Building WordPress plugins & devtools | Founder @cirvgreen | 50+ open-source CLI tools","2026-10-21 23:37:12",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add NickCirv\u002Fengram --skill mistakes",{"tool":51,"command":52},"bunx","bunx skills add NickCirv\u002Fengram --skill mistakes",{"tool":54,"command":55},"pnpm","pnpm dlx skills add NickCirv\u002Fengram --skill mistakes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNickCirv\u002Fengram\u002Fblob\u002Fmain\u002Fplugins\u002Fanthropic-marketplace\u002Fengram\u002Fskills\u002Fmistakes\u002FSKILL.md",true,[],[60,83,107,137,151,157],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":71,"publishedAt":31},"01M6PFJZDQTRZ7PK0C8BAEB2VS","content-strategy-?","Use when planning content calendars. Triggers: “content strategy”, ‘editorial calendar’. Also triggers on \"content audit\".","https:\u002F\u002Fgithub.com\u002FNickCirv\u002Fengram\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Funicode\u002FSKILL.md",[66],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[72,73,74,75,76,77,78,79,80,81,24,82],"content strategy ?","strategy","content strategy","content","content audit","editorial calendar","planning","audit","editorial","triggers","calendar",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":94,"publishedAt":31},"01M6PFJVQT6HSEY7842DJGQYC2","copywriting","Use when writing, rewriting, or improving marketing copy for landing pages, homepages, or product pages. Triggers: 'write copy for', 'improve this copy'. Do NOT use for email copy — use email-marketing instead.","https:\u002F\u002Fgithub.com\u002FNickCirv\u002Fengram\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fnormal\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",[85,95,96,24,97,98,81,99,100,101,102,103,104,105,106],"marketing","landing","do","pages","copy","email-marketing","for","write","writing","product","email","improve",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":119,"publishedAt":31},"01M6PFJQHGKDZNRYGCB8DSTZDV","nodejs-backend-patterns","Use when building production Node.js backends with Express or Fastify. Also use when hardening a Node.js service for production. Do NOT use for frontend React — use scaffolding-react-components instead.","https:\u002F\u002Fgithub.com\u002FNickCirv\u002Fengram\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fmultiline\u002FSKILL.md",[113,116],{"categoryNo":114,"categoryName":115,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":117,"categoryName":118,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000010","后端与接口",[120,121,122,123,124,125,126,127,128,129,130,131,24,132,97,133,134,135,136,101],"nodejs backend","patterns","backend","backend patterns","nodejs backend patterns","nodejs","express","hardening","Production","react","components","node","frontend","scaffolding","frontend react","fastify","with",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":146,"publishedAt":31},"01M6PFJJAGNYVXX9FYWDR40ZCT","placeholder-skill","Placeholder skill with frontmatter only, no body content.","https:\u002F\u002Fgithub.com\u002FNickCirv\u002Fengram\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fempty-body\u002FSKILL.md",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发",[147,148,149,75,150,136],"placeholder skill","placeholder","only","frontmatter",{"skillNo":152,"name":153,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":31},"01M6PFJDDDTW0E0TT1F1C9AWZC","corrupted","https:\u002F\u002Fgithub.com\u002FNickCirv\u002Fengram\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fcorrupted\u002FSKILL.md",[],[153],{"skillNo":158,"name":159,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":31},"01M6PFJAEG0BJFZM26SWPXMVM7","anomaly","https:\u002F\u002Fgithub.com\u002FNickCirv\u002Fengram\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fanomaly\u002FSKILL.md",[],[159]]