[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75C9QZQXAXT8BE7CY6PWWGT":3,"skill-same:01M75C9QZQXAXT8BE7CY6PWWGT":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},"01M75C9QZQXAXT8BE7CY6PWWGT","client-comms-log",null,"Log a client communication — call, email, text, letter, in-person, voicemail. Append-only per-case record with dated entries, direction, medium, summary, action items. Works alongside \u002Fclient-letter and \u002Fstatus client. Use when logging a call or client email, reviewing a communication log, or asking \"what did we tell [client] last time\".","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\u002Fclient-comms-log\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: client-comms-log\ndescription: >\n  Log a client communication — call, email, text, letter, in-person, voicemail.\n  Append-only per-case record with dated entries, direction, medium, summary,\n  action items. Works alongside \u002Fclient-letter and \u002Fstatus client. Use when\n  logging a call or client email, reviewing a communication log, or asking\n  \"what did we tell [client] last time\".\nargument-hint: \"[case-id] [--add (default) | --read | --summary | --patterns]\"\n---\n\n# \u002Fclient-comms-log\n\n1. Use the workflow below.\n2. Require case-id (prompt if not provided).\n3. Route by flag:\n   - `--add` (default): capture direction, medium, student, summary, action items, follow-up due. Confirm with user. Append (prepend most-recent-first) to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flegal-clinic\u002Fclient-comms\u002F[case-id]\u002Flog.md`.\n   - `--read`: show the most recent N entries.\n   - `--summary`: one-paragraph condensed read.\n   - `--patterns`: scan for unanswered comms, missed follow-ups, language gaps, tone shifts, contact gaps. Supervision-oriented.\n4. Integration: offer `\u002Flegal-clinic:deadlines --add` if the log establishes a deadline; route to `\u002Flegal-clinic:semester-handoff` via `--summary` when relevant.\n\n---\n\n# Client Communications Log\n\n## Purpose\n\nFour reasons to keep this log:\n\n1. **Malpractice defense.** If a client claims \"no one ever told me [X],\" a dated entry showing otherwise is the answer. Clinical professors carry professional liability on student work; contemporaneous records protect them.\n2. **Continuity at handoff.** The next semester's student takes over and reads the log; they don't re-ask the client questions already answered.\n3. **Supervision visibility.** Five unreturned voicemails over six weeks is a pattern. The log makes patterns visible that individual students might not flag on their own.\n4. **File retention.** Law school clinics have obligations to maintain complete client files. Communication history is part of that.\n\nLight. Append-only. The student's job is to write a two-sentence entry after every contact; the skill formats it and appends.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flegal-clinic\u002Fclient-comms\u002F[case-id]\u002Flog.md` (if exists) — append target\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flegal-clinic\u002FCLAUDE.md` → not heavily read; this skill is case-scoped\n\n## Modes\n\nFlag: `--add | --read | --summary | --patterns` (default: add)\n\n### `--add` (default) — log a new entry\n\n**Inputs:**\n- Case ID (required — which case)\n- Date + time (default: now)\n- Direction: `in` (client → clinic) | `out` (clinic → client)\n- Medium: `call | email | text | letter | in-person | video | voicemail-left | voicemail-received`\n- Who (student): name\n- Who (client side): client name, or \"third-party: [description]\" if from opposing counsel, family member, etc.\n- Duration \u002F length (e.g., \"10 min call\", \"3-paragraph email\", \"45 min in-person meeting\")\n- Summary: 2-4 sentences. What happened, what was substantive.\n- Action items:\n  - What the student owes the client (with deadline)\n  - What the client owes the student (with expected timing)\n- Follow-up due: date if applicable\n- Notes: anything that matters but doesn't fit above — language used, emotional tone, family dynamic observed\n\n**Before writing:** show the user the formatted entry and ask for confirmation. Clinic records should be reviewed before they're written, not after.\n\n**Append** to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flegal-clinic\u002Fclient-comms\u002F[case-id]\u002Flog.md`. If the log doesn't exist, create it with a header:\n\n```markdown\n# Communications Log — [case name]\n\n**Case ID:** [case-id]\n**Client:** [name]\n**Opened:** [YYYY-MM-DD]\n\nAppend-only. Most recent at top.\n\n---\n```\n\nThen prepend new entries at the top (most recent first).\n\n### `--read` — show recent entries\n\nPrint the most recent N entries (default 5). Useful when picking up a case mid-semester or before a client call.\n\n### `--summary` — condensed read\n\nProduce a one-paragraph summary of the log — most recent contact, total entries, common medium, any open action items from the student side, any unanswered communications. Feeds `\u002Fsemester-handoff` and `\u002Fstatus`.\n\n### `--patterns` — flag concerns across the log\n\nScan for:\n\n- **Unanswered communications from client.** Client called or emailed N times without a response entry.\n- **Missed follow-up.** Action item with follow-up due date, and no later entry resolving it.\n- **Language \u002F accommodation issues.** Client language noted as non-English; check whether outgoing communications have been in that language.\n- **Escalation patterns.** Client tone shifting (frustrated \u002F distressed) across entries.\n- **Gaps.** Long stretches with no contact on an active case.\n\nThis is a supervision tool. Clinical professors running `--patterns` across their cases see which students might need support.\n\n## Integration\n\n- **`\u002Fclient-letter`:** after generating and sending a letter, offer to log it as an outgoing comm.\n- **`\u002Fstatus client`:** when producing a client-facing status summary, offer to log it (often these summaries go to clients).\n- **`\u002Fclient-intake`:** first entry in every new case's log is the intake contact.\n- **`\u002Fsemester-handoff`:** handoff memos read `--summary` for each case to populate the communications-history section.\n- **`\u002Fdeadlines`:** if a communication established a deadline (\"client said they need to respond by Friday\"), offer to `\u002Fdeadlines --add`.\n\n## What this skill does not do\n\n- **Store substantive legal analysis.** That lives in intake, memo, and status files. The log is communication record — facts of contact, not legal strategy.\n- **Auto-log from outside systems.** If the clinic uses a case management system (Clio), an integration could pull call logs and emails automatically. That's a future add; not v1.\n- **Edit past entries.** Append-only. If an entry is wrong, write a new entry referencing and correcting it. The integrity of the log depends on not rewriting history.\n- **Enforce log discipline.** If a student doesn't log a call, the skill can't know. Log hygiene is a clinic-culture problem; the skill just makes logging easy.\n- **Handle privileged or attorney-only notes.** If the student needs to record strategic thinking, that goes in the case's internal analysis file, not the comms log.\n","# \u002Fclient-comms-log\n\n1. Use the workflow below.\n2. Require case-id (prompt if not provided).\n3. Route by flag:\n   - `--add` (default): capture direction, medium, student, summary, action items, follow-up due. Confirm with user. Append (prepend most-recent-first) to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flegal-clinic\u002Fclient-comms\u002F[case-id]\u002Flog.md`.\n   - `--read`: show the most recent N entries.\n   - `--summary`: one-paragraph condensed read.\n   - `--patterns`: scan for unanswered comms, missed follow-ups, language gaps, tone shifts, contact gaps. Supervision-oriented.\n4. Integration: offer `\u002Flegal-clinic:deadlines --add` if the log establishes a deadline; route to `\u002Flegal-clinic:semester-handoff` via `--summary` when relevant.\n\n---\n\n# Client Communications Log\n\n## Purpose\n\nFour reasons to keep this log:\n\n1. **Malpractice defense.** If a client claims \"no one ever told me [X],\" a dated entry showing otherwise is the answer. Clinical professors carry professional liability on student work; contemporaneous records protect them.\n2. **Continuity at handoff.** The next semester's student takes over and reads the log; they don't re-ask the client questions already answered.\n3. **Supervision visibility.** Five unreturned voicemails over six weeks is a pattern. The log makes patterns visible that individual students might not flag on their own.\n4. **File retention.** Law school clinics have obligations to maintain complete client files. Communication history is part of that.\n\nLight. Append-only. The student's job is to write a two-sentence entry after every contact; the skill formats it and appends.\n\n## Load context\n\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flegal-clinic\u002Fclient-comms\u002F[case-id]\u002Flog.md` (if exists) — append target\n- `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flegal-clinic\u002FCLAUDE.md` → not heavily read; this skill is case-scoped\n\n## Modes\n\nFlag: `--add | --read | --summary | --patterns` (default: add)\n\n### `--add` (default) — log a new entry\n\n**Inputs:**\n- Case ID (required — which case)\n- Date + time (default: now)\n- Direction: `in` (client → clinic) | `out` (clinic → client)\n- Medium: `call | email | text | letter | in-person | video | voicemail-left | voicemail-received`\n- Who (student): name\n- Who (client side): client name, or \"third-party: [description]\" if from opposing counsel, family member, etc.\n- Duration \u002F length (e.g., \"10 min call\", \"3-paragraph email\", \"45 min in-person meeting\")\n- Summary: 2-4 sentences. What happened, what was substantive.\n- Action items:\n  - What the student owes the client (with deadline)\n  - What the client owes the student (with expected timing)\n- Follow-up due: date if applicable\n- Notes: anything that matters but doesn't fit above — language used, emotional tone, family dynamic observed\n\n**Before writing:** show the user the formatted entry and ask for confirmation. Clinic records should be reviewed before they're written, not after.\n\n**Append** to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Flegal-clinic\u002Fclient-comms\u002F[case-id]\u002Flog.md`. If the log doesn't exist, create it with a header:\n\n```markdown\n# Communications Log — [case name]\n\n**Case ID:** [case-id]\n**Client:** [name]\n**Opened:** [YYYY-MM-DD]\n\nAppend-only. Most recent at top.\n\n---\n```\n\nThen prepend new entries at the top (most recent first).\n\n### `--read` — show recent entries\n\nPrint the most recent N entries (default 5). Useful when picking up a case mid-semester or before a client call.\n\n### `--summary` — condensed read\n\nProduce a one-paragraph summary of the log — most recent contact, total entries, common medium, any open action items from the student side, any unanswered communications. Feeds `\u002Fsemester-handoff` and `\u002Fstatus`.\n\n### `--patterns` — flag concerns across the log\n\nScan for:\n\n- **Unanswered communications from client.** Client called or emailed N times without a response entry.\n- **Missed follow-up.** Action item with follow-up due date, and no later entry resolving it.\n- **Language \u002F accommodation issues.** Client language noted as non-English; check whether outgoing communications have been in that language.\n- **Escalation patterns.** Client tone shifting (frustrated \u002F distressed) across entries.\n- **Gaps.** Long stretches with no contact on an active case.\n\nThis is a supervision tool. Clinical professors running `--patterns` across their cases see which students might need support.\n\n## Integration\n\n- **`\u002Fclient-letter`:** after generating and sending a letter, offer to log it as an outgoing comm.\n- **`\u002Fstatus client`:** when producing a client-facing status summary, offer to log it (often these summaries go to clients).\n- **`\u002Fclient-intake`:** first entry in every new case's log is the intake contact.\n- **`\u002Fsemester-handoff`:** handoff memos read `--summary` for each case to populate the communications-history section.\n- **`\u002Fdeadlines`:** if a communication established a deadline (\"client said they need to respond by Friday\"), offer to `\u002Fdeadlines --add`.\n\n## What this skill does not do\n\n- **Store substantive legal analysis.** That lives in intake, memo, and status files. The log is communication record — facts of contact, not legal strategy.\n- **Auto-log from outside systems.** If the clinic uses a case management system (Clio), an integration could pull call logs and emails automatically. That's a future add; not v1.\n- **Edit past entries.** Append-only. If an entry is wrong, write a new entry referencing and correcting it. The integrity of the log depends on not rewriting history.\n- **Enforce log discipline.** If a student doesn't log a call, the skill can't know. Log hygiene is a clinic-culture problem; the skill just makes logging easy.\n- **Handle privileged or attorney-only notes.** If the student needs to record strategic thinking, that goes in the case's internal analysis file, not the comms log.\n",{"name":5,"description":23,"argument-hint":24},"Log a client communication — call, email, text, letter, in-person, voicemail. Append-only per-case record with dated entries, direction, medium, summary, action items. Works alongside \u002Fclient-letter and \u002Fstatus client. Use when logging a call or client email, reviewing a communication log, or asking \"what did we tell [client] last time\".\n","[case-id] [--add (default) | --read | --summary | --patterns]","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fclient-comms-log",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 client-comms-log",{"tool":40,"command":41},"bunx","bunx skills add agisota\u002Fold-one --skill client-comms-log",{"tool":43,"command":44},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill client-comms-log","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fclient-comms-log\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",[],[]]