[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75ESW4RCS86K50AAC8SW0GD":3,"skill-same:01M75ESW4RCS86K50AAC8SW0GD":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M75ESW4RCS86K50AAC8SW0GD","irac-practice",null,"Grade an IRAC essay for structure, issue-spotting, rule accuracy, analysis depth, and organization. Does NOT rewrite the essay or show a model answer; tracks patterns across sessions. Use when the user says \"grade my IRAC\", \"check my essay\", or \"I wrote this, give me feedback\".","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Firac-practice\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: irac-practice\ndescription: >\n  Grade an IRAC essay for structure, issue-spotting, rule accuracy, analysis\n  depth, and organization. Does NOT rewrite the essay or show a model answer;\n  tracks patterns across sessions. Use when the user says \"grade my IRAC\",\n  \"check my essay\", or \"I wrote this, give me feedback\".\nargument-hint: \"[paste essay OR path to draft OR --generate-hypo]\"\n---\n\n# \u002Firac-practice\n\n1. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002FCLAUDE.md` → classes, exam formats, outline locations, learning style.\n2. Apply the framework below.\n3. Establish mode: student-provided hypo + answer, OR skill-generated hypo with student's answer.\n4. Read the answer closely. Map against expected IRAC components.\n5. Output structured feedback: issues spotted\u002Fmissed, rule accuracy, analysis depth, organization, grade band, top 3 fixes, at most 1-2 labeled example phrasings (never a full IRAC model).\n6. Append to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002Firac-sessions\u002F[student]\u002Ftracker.md` for pattern detection. Surface patterns after 3+ sessions.\n\n---\n\n## Real-matter check\n\nIf the question the student is asking sounds like it's about a REAL situation — their lease, their parking ticket, their family's business, their friend's arrest, a real dollar amount, a real deadline, a real party name — stop.\n\n> \"This sounds like a real situation, not a hypothetical. I can't give you legal advice, and you can't give it either — you're not a lawyer yet. If this is real, [the person] needs an actual lawyer: legal aid, your school's clinic, a lawyer referral service (your jurisdiction's bar association, law society, or legal aid body), or (if there's money) a private attorney. I'm happy to help you understand the general legal concepts involved, but that's study, not advice.\"\n\nWatch for: real names, real addresses, real dates, specific dollar amounts, \"my landlord\u002Fboss\u002Fparent\u002Ffriend,\" \"I got a ticket\u002Fletter\u002Fnotice,\" deadlines measured in days. Any one of these is a trigger.\n\n## Purpose\n\n1L writing is mostly IRAC. 2L-3L writing that touches legal analysis is IRAC under the hood. The exam rewards structure as much as content. This skill grades *structure* — did you spot the issues, did you state the rules correctly, did you apply rules to facts or just restate both?\n\n**Does not rewrite the essay.** Ever. The whole point is that you learn by writing, getting specific structural feedback, and rewriting yourself.\n\n## Confidence discipline\n\n- Structure grading (did you IRAC? did you organize? did you use topic sentences?) — confident. Structure is structure.\n- Issue-spotting feedback (did you spot the issue presented?) — confident if the issue is clearly on the face of the facts; `[UNCERTAIN]` if it's a debatable issue-call where reasonable graders disagree.\n- Rule-accuracy grading — I check rules against my knowledge and flag `[VERIFY]` on anything I'm not certain about. I do not silently fail your correct rule statement because I wasn't sure.\n- If the hypo is from a jurisdiction or area I don't know well, I grade structure only and say so explicitly — \"I can grade your IRAC shape but I can't independently verify the rules for [area]. Cross-check with your outline.\"\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002FCLAUDE.md` → current classes, exam formats, outline locations, learning style\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002Firac-sessions\u002F[student]\u002Ftracker.md` if exists — pattern tracking across sessions\n- Student-provided hypo (if practicing on a specific prompt) and their written answer\n\n## Workflow\n\n### Step 1: Establish what we're grading\n\nTwo modes:\n\n- **Student-provided hypo:** user pastes (or points at) a hypo they're practicing on, then pastes their answer. Skill grades against the hypo.\n- **Skill-generated hypo:** user asks for practice; skill generates a hypo in their subject area, user writes the answer, skill grades.\n\nIf skill-generated, the hypo itself follows the same confidence rules — the skill flags any sub-issue it's less confident about.\n\n### Step 2: Read the answer closely\n\nDon't skim. Read the student's answer as if grading it. Map it against expected IRAC components:\n\n- **Issues:** what issues did they spot? (List them.) What issues are in the hypo that they didn't spot?\n- **Rules:** for each issue addressed, is the rule statement (a) present, (b) accurate, (c) complete?\n- **Application:** for each rule, did the student apply to the specific facts, or just repeat rule + facts without linking? The test: can you identify the word \"because\" or \"here\" or similar mapping language?\n- **Conclusion:** did they reach one? Is it responsive to the call?\n- **Organization:** IRAC \u002F CRAC order? Topic sentences? Paragraph breaks that make sense?\n\n### Step 3: Structured feedback\n\nOutput per component. No rewriting. Specific, not generic.\n\n```markdown\n# IRAC Grade — [date]\n\n**Hypo:** [summary or pointer]\n**Student answer length:** [N words]\n**Expected issues:** [list — from the hypo]\n\n---\n\n## Issue spotting\n\n**Spotted:** [list]\n**Missed:** [list — these are points left on the table]\n**Mis-identified:** [if the student called something an issue that isn't]\n\n[If an issue is [UNCERTAIN: debatable issue-call], note: \"your grader might agree or disagree here; defensible read.\"]\n\n## Rule statements\n\nFor each issue addressed:\n\n- **[Issue 1]:** [Accurate \u002F partially correct \u002F wrong \u002F missing element] — [what's off, one sentence] — [VERIFY if skill less than confident on rule]\n- **[Issue 2]:** ...\n\n## Analysis\n\nFor each rule the student stated:\n\n- **[Issue 1] — did you apply?** [Yes, applied to [specific facts] | Partially — you mentioned [facts] but didn't link to rule element | No — you restated rule then facts without mapping]\n- [If not applied well: \"what you needed to do: connect [specific fact] to [specific rule element]. Not 'defendant acted negligently because of the facts' — 'defendant breached the duty of care because [specific fact] means [specific conclusion about the element].'\"]\n\n## Organization\n\n- **Order:** IRAC? CRAC? Something else?\n- **Paragraph structure:** topic sentence leading? Or buried?\n- **Transitions:** do issues flow, or is it a wall of text?\n- **Call responsiveness:** did you answer what was asked?\n\n## If graded\n\nA rough calibration — not a precise score, but a band:\n\n- **If this were graded today: [Pass \u002F borderline \u002F not yet]** — reasoning in one sentence\n\n## Top three fixes\n\nRank-ordered, one sentence each. What to rewrite if you only had time for three changes.\n\n1.\n2.\n3.\n\n## Citation check\n\nAny cases, statutes, or rules referenced in this feedback were generated by an AI model and have not been verified. Before you rely on them in a rewrite or a graded essay, look them up on Westlaw, Fastcase, CourtListener, or your school's research tool. AI-generated citations are sometimes fabricated or misquoted.\n\n## Writing sample — labeled example only (do not copy)\n\nIf there's a specific structural move the student missed (e.g., rule-application mapping), show ONE example sentence or paragraph that illustrates the move. Explicitly label it:\n\n> \"Here's one way to frame an analysis sentence — write your own version, don't copy this:\n> [example]\"\n\nUse sparingly. One per grade, max two. Never a full IRAC example.\n\n**Never on the student's actual substantive issue.** Example phrasings illustrate the structural move in generic placeholder form (e.g., \"[fact] means [conclusion about element] because [reasoning]\"). They cannot show what an analysis sentence or paragraph would look like on the exact hypo or issue the student is writing about — that crosses from \"seeing the move\" into \"being handed the answer.\" If the student is writing about negligence in a car accident hypo, the example must use a different subject area or abstract placeholders, not a negligence analysis sentence.\n```\n\n### Step 4: Track patterns\n\nAppend to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002Firac-sessions\u002F[student]\u002Ftracker.md`:\n\n```markdown\n## [date] — [subject \u002F hypo topic]\n- Issues missed: [list]\n- Rule accuracy: [% or qualitative]\n- Analysis gap: [specific pattern — e.g., \"restates rule without applying\"]\n- Organization: [ok \u002F weak \u002F strong]\n```\n\nAfter 3+ sessions, surface patterns:\n- \"You keep missing counterarguments — three sessions in a row.\"\n- \"You're strong on Issue + Rule but consistently weak on Application.\"\n- \"Your organization is strong; the gap is at rule-accuracy. Drill black-letter rules with \u002Flaw-student:flashcards.\"\n\nPattern detection is the long-term value of this skill. One-off feedback helps one essay; pattern feedback changes how you study.\n\n## Integration with other skills\n\n- **legal-writing:** for non-IRAC writing (memos, briefs, papers), use `\u002Flaw-student:legal-writing` instead\n- **socratic-drill:** if issue-spotting is the recurring gap, `\u002Flaw-student:socratic-drill` on issue-spotting for the subject before more essay practice\n- **flashcards:** if rule accuracy is the gap, flashcards are the right tool\n- **outline-builder:** if the student's rule is genuinely wrong in their outline, fixing the outline fixes many future IRACs\n\n## Close with the next-steps decision tree\n\nEnd with the next-steps decision tree per CLAUDE.md `## Outputs`. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.\n\n## What this skill does not do\n\n- **Rewrite the student's answer.** Ever. No exceptions. Labeled example phrasings (one or two, clearly marked) are permitted to illustrate a structural move; they cannot be copied into the student's answer.\n- **Show a model answer.** The student has to build the model in their head. Showing one short-circuits the learning.\n- **Grade content correctness on jurisdictions or areas the skill doesn't know well.** In those cases, skill grades structure only and says so — \"I can grade your IRAC shape but can't verify rules here.\"\n- **Give a precise numeric score.** Pass\u002Fborderline\u002Fnot-yet bands only. Grading is qualitative; precision is false precision.\n- **Substitute for a professor's grading.** Professors have rubrics and preferences this skill doesn't know. Use feedback to improve; don't treat it as the final word.\n","# \u002Firac-practice\n\n1. Load `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002FCLAUDE.md` → classes, exam formats, outline locations, learning style.\n2. Apply the framework below.\n3. Establish mode: student-provided hypo + answer, OR skill-generated hypo with student's answer.\n4. Read the answer closely. Map against expected IRAC components.\n5. Output structured feedback: issues spotted\u002Fmissed, rule accuracy, analysis depth, organization, grade band, top 3 fixes, at most 1-2 labeled example phrasings (never a full IRAC model).\n6. Append to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002Firac-sessions\u002F[student]\u002Ftracker.md` for pattern detection. Surface patterns after 3+ sessions.\n\n---\n\n## Real-matter check\n\nIf the question the student is asking sounds like it's about a REAL situation — their lease, their parking ticket, their family's business, their friend's arrest, a real dollar amount, a real deadline, a real party name — stop.\n\n> \"This sounds like a real situation, not a hypothetical. I can't give you legal advice, and you can't give it either — you're not a lawyer yet. If this is real, [the person] needs an actual lawyer: legal aid, your school's clinic, a lawyer referral service (your jurisdiction's bar association, law society, or legal aid body), or (if there's money) a private attorney. I'm happy to help you understand the general legal concepts involved, but that's study, not advice.\"\n\nWatch for: real names, real addresses, real dates, specific dollar amounts, \"my landlord\u002Fboss\u002Fparent\u002Ffriend,\" \"I got a ticket\u002Fletter\u002Fnotice,\" deadlines measured in days. Any one of these is a trigger.\n\n## Purpose\n\n1L writing is mostly IRAC. 2L-3L writing that touches legal analysis is IRAC under the hood. The exam rewards structure as much as content. This skill grades *structure* — did you spot the issues, did you state the rules correctly, did you apply rules to facts or just restate both?\n\n**Does not rewrite the essay.** Ever. The whole point is that you learn by writing, getting specific structural feedback, and rewriting yourself.\n\n## Confidence discipline\n\n- Structure grading (did you IRAC? did you organize? did you use topic sentences?) — confident. Structure is structure.\n- Issue-spotting feedback (did you spot the issue presented?) — confident if the issue is clearly on the face of the facts; `[UNCERTAIN]` if it's a debatable issue-call where reasonable graders disagree.\n- Rule-accuracy grading — I check rules against my knowledge and flag `[VERIFY]` on anything I'm not certain about. I do not silently fail your correct rule statement because I wasn't sure.\n- If the hypo is from a jurisdiction or area I don't know well, I grade structure only and say so explicitly — \"I can grade your IRAC shape but I can't independently verify the rules for [area]. Cross-check with your outline.\"\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002FCLAUDE.md` → current classes, exam formats, outline locations, learning style\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002Firac-sessions\u002F[student]\u002Ftracker.md` if exists — pattern tracking across sessions\n- Student-provided hypo (if practicing on a specific prompt) and their written answer\n\n## Workflow\n\n### Step 1: Establish what we're grading\n\nTwo modes:\n\n- **Student-provided hypo:** user pastes (or points at) a hypo they're practicing on, then pastes their answer. Skill grades against the hypo.\n- **Skill-generated hypo:** user asks for practice; skill generates a hypo in their subject area, user writes the answer, skill grades.\n\nIf skill-generated, the hypo itself follows the same confidence rules — the skill flags any sub-issue it's less confident about.\n\n### Step 2: Read the answer closely\n\nDon't skim. Read the student's answer as if grading it. Map it against expected IRAC components:\n\n- **Issues:** what issues did they spot? (List them.) What issues are in the hypo that they didn't spot?\n- **Rules:** for each issue addressed, is the rule statement (a) present, (b) accurate, (c) complete?\n- **Application:** for each rule, did the student apply to the specific facts, or just repeat rule + facts without linking? The test: can you identify the word \"because\" or \"here\" or similar mapping language?\n- **Conclusion:** did they reach one? Is it responsive to the call?\n- **Organization:** IRAC \u002F CRAC order? Topic sentences? Paragraph breaks that make sense?\n\n### Step 3: Structured feedback\n\nOutput per component. No rewriting. Specific, not generic.\n\n```markdown\n# IRAC Grade — [date]\n\n**Hypo:** [summary or pointer]\n**Student answer length:** [N words]\n**Expected issues:** [list — from the hypo]\n\n---\n\n## Issue spotting\n\n**Spotted:** [list]\n**Missed:** [list — these are points left on the table]\n**Mis-identified:** [if the student called something an issue that isn't]\n\n[If an issue is [UNCERTAIN: debatable issue-call], note: \"your grader might agree or disagree here; defensible read.\"]\n\n## Rule statements\n\nFor each issue addressed:\n\n- **[Issue 1]:** [Accurate \u002F partially correct \u002F wrong \u002F missing element] — [what's off, one sentence] — [VERIFY if skill less than confident on rule]\n- **[Issue 2]:** ...\n\n## Analysis\n\nFor each rule the student stated:\n\n- **[Issue 1] — did you apply?** [Yes, applied to [specific facts] | Partially — you mentioned [facts] but didn't link to rule element | No — you restated rule then facts without mapping]\n- [If not applied well: \"what you needed to do: connect [specific fact] to [specific rule element]. Not 'defendant acted negligently because of the facts' — 'defendant breached the duty of care because [specific fact] means [specific conclusion about the element].'\"]\n\n## Organization\n\n- **Order:** IRAC? CRAC? Something else?\n- **Paragraph structure:** topic sentence leading? Or buried?\n- **Transitions:** do issues flow, or is it a wall of text?\n- **Call responsiveness:** did you answer what was asked?\n\n## If graded\n\nA rough calibration — not a precise score, but a band:\n\n- **If this were graded today: [Pass \u002F borderline \u002F not yet]** — reasoning in one sentence\n\n## Top three fixes\n\nRank-ordered, one sentence each. What to rewrite if you only had time for three changes.\n\n1.\n2.\n3.\n\n## Citation check\n\nAny cases, statutes, or rules referenced in this feedback were generated by an AI model and have not been verified. Before you rely on them in a rewrite or a graded essay, look them up on Westlaw, Fastcase, CourtListener, or your school's research tool. AI-generated citations are sometimes fabricated or misquoted.\n\n## Writing sample — labeled example only (do not copy)\n\nIf there's a specific structural move the student missed (e.g., rule-application mapping), show ONE example sentence or paragraph that illustrates the move. Explicitly label it:\n\n> \"Here's one way to frame an analysis sentence — write your own version, don't copy this:\n> [example]\"\n\nUse sparingly. One per grade, max two. Never a full IRAC example.\n\n**Never on the student's actual substantive issue.** Example phrasings illustrate the structural move in generic placeholder form (e.g., \"[fact] means [conclusion about element] because [reasoning]\"). They cannot show what an analysis sentence or paragraph would look like on the exact hypo or issue the student is writing about — that crosses from \"seeing the move\" into \"being handed the answer.\" If the student is writing about negligence in a car accident hypo, the example must use a different subject area or abstract placeholders, not a negligence analysis sentence.\n```\n\n### Step 4: Track patterns\n\nAppend to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flaw-student\u002Firac-sessions\u002F[student]\u002Ftracker.md`:\n\n```markdown\n## [date] — [subject \u002F hypo topic]\n- Issues missed: [list]\n- Rule accuracy: [% or qualitative]\n- Analysis gap: [specific pattern — e.g., \"restates rule without applying\"]\n- Organization: [ok \u002F weak \u002F strong]\n```\n\nAfter 3+ sessions, surface patterns:\n- \"You keep missing counterarguments — three sessions in a row.\"\n- \"You're strong on Issue + Rule but consistently weak on Application.\"\n- \"Your organization is strong; the gap is at rule-accuracy. Drill black-letter rules with \u002Flaw-student:flashcards.\"\n\nPattern detection is the long-term value of this skill. One-off feedback helps one essay; pattern feedback changes how you study.\n\n## Integration with other skills\n\n- **legal-writing:** for non-IRAC writing (memos, briefs, papers), use `\u002Flaw-student:legal-writing` instead\n- **socratic-drill:** if issue-spotting is the recurring gap, `\u002Flaw-student:socratic-drill` on issue-spotting for the subject before more essay practice\n- **flashcards:** if rule accuracy is the gap, flashcards are the right tool\n- **outline-builder:** if the student's rule is genuinely wrong in their outline, fixing the outline fixes many future IRACs\n\n## Close with the next-steps decision tree\n\nEnd with the next-steps decision tree per CLAUDE.md `## Outputs`. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.\n\n## What this skill does not do\n\n- **Rewrite the student's answer.** Ever. No exceptions. Labeled example phrasings (one or two, clearly marked) are permitted to illustrate a structural move; they cannot be copied into the student's answer.\n- **Show a model answer.** The student has to build the model in their head. Showing one short-circuits the learning.\n- **Grade content correctness on jurisdictions or areas the skill doesn't know well.** In those cases, skill grades structure only and says so — \"I can grade your IRAC shape but can't verify rules here.\"\n- **Give a precise numeric score.** Pass\u002Fborderline\u002Fnot-yet bands only. Grading is qualitative; precision is false precision.\n- **Substitute for a professor's grading.** Professors have rubrics and preferences this skill doesn't know. Use feedback to improve; don't treat it as the final word.\n",{"name":5,"description":23,"argument-hint":24},"Grade an IRAC essay for structure, issue-spotting, rule accuracy, analysis depth, and organization. Does NOT rewrite the essay or show a model answer; tracks patterns across sessions. Use when the user says \"grade my IRAC\", \"check my essay\", or \"I wrote this, give me feedback\".\n","[paste essay OR path to draft OR --generate-hypo]","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Firac-practice",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add agisota\u002Fold-one --skill irac-practice",{"tool":40,"command":41},"bunx","bunx skills add agisota\u002Fold-one --skill irac-practice",{"tool":43,"command":44},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill irac-practice","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Firac-practice\u002FSKILL.md",true,[],[49,56,63,72,79,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":67,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]