[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75K2ZVW3CT0CPADVZ482D39":3,"skill-same:01M75K2ZVW3CT0CPADVZ482D39":46},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75K2ZVW3CT0CPADVZ482D39","team-communications",null,"Write internal company communications — 3P updates (Progress\u002FPlans\u002FProblems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms. Use this skill any time the user asks to draft, edit, or format something meant for internal audiences. Trigger on keywords like \"3P\", \"weekly update\", \"newsletter\", \"FAQ\", \"internal comms\", \"status report\", \"company update\", \"team update\", \"incident report\", or any request to summarize work for leadership, teammates, or the broader company. Even casual requests like \"write my update\" or \"summarize what my team did this week\" should trigger this skill.","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\u002Fteam-communications\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: team-communications\ndescription: Write internal company communications — 3P updates (Progress\u002FPlans\u002FProblems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms. Use this skill any time the user asks to draft, edit, or format something meant for internal audiences. Trigger on keywords like \"3P\", \"weekly update\", \"newsletter\", \"FAQ\", \"internal comms\", \"status report\", \"company update\", \"team update\", \"incident report\", or any request to summarize work for leadership, teammates, or the broader company. Even casual requests like \"write my update\" or \"summarize what my team did this week\" should trigger this skill.\n---\n\n# Internal Comms\n\n> Originally contributed by [maximcoding](https:\u002F\u002Fgithub.com\u002Fmaximcoding) — enhanced and integrated by the claude-skills team.\n\nWrite polished internal communications by loading the right reference file, gathering context, and outputting in the company's exact format.\n\n## Routing\n\nIdentify the communication type from the user's request, then read the matching reference file before writing anything:\n\n| Type | Trigger phrases | Reference file |\n|---|---|---|\n| **3P Update** | \"3P\", \"progress plans problems\", \"weekly team update\", \"what did we ship\" | `references\u002F3p-updates.md` |\n| **Newsletter** | \"newsletter\", \"company update\", \"weekly\u002Fmonthly roundup\", \"all-hands summary\" | `references\u002Fcompany-newsletter.md` |\n| **FAQ** | \"FAQ\", \"common questions\", \"what people are asking\", \"confusion around\" | `references\u002Ffaq-answers.md` |\n| **General** | anything internal that doesn't match above | `references\u002Fgeneral-comms.md` |\n\nIf the type is ambiguous, ask one clarifying question — don't guess.\n\n## Workflow\n\n1. **Read the reference file** for the matched type. Follow its formatting exactly.\n2. **Gather inputs.** Use available MCP tools (Slack, Gmail, Google Drive, Calendar) to pull real data. If no tools are connected, ask the user to provide bullet points or raw context.\n3. **Clarify scope.** Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.\n4. **Draft.** Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.\n5. **Present the draft** and ask if anything needs to be added, removed, or reworded.\n\n## Tone & Style (applies to all types)\n\n- Use \"we\" — you are part of the company.\n- Active voice, present tense for progress, future tense for plans.\n- Concise. Every sentence should carry information. Cut filler.\n- Include metrics and links wherever possible.\n- Professional but approachable — not corporate-speak.\n- Put the most important information first.\n\n## When tools are unavailable\n\nIf the user hasn't connected Slack, Gmail, Drive, or Calendar, don't stall. Ask them to paste or describe what they want covered. You're formatting and sharpening — that's still valuable. Mention which tools would improve future drafts so they can connect them later.\n\n---\n\n## Anti-Patterns\n\n| Anti-Pattern | Why It Fails | Better Approach |\n|---|---|---|\n| Writing updates without reading the reference template first | Output won't match company format — user has to reformat | Always load the matching reference file before drafting |\n| Inventing metrics or accomplishments | Internal comms must be factual — fabrication destroys trust | Only include data the user provided or MCP tools retrieved |\n| Using passive voice for accomplishments | \"The feature was shipped\" hides who did the work | \"Team X shipped the feature\" — active voice credits the team |\n| Writing walls of text for status updates | Leadership scans, doesn't read — key info gets buried | Lead with the headline, follow with 3-5 bullet points |\n| Sending without confirming audience | A team update reads differently from a company-wide newsletter | Always confirm: who will read this? |\n\n---\n\n## Related Skills\n\n| Skill | Relationship |\n|-------|-------------|\n| `project-management\u002Fsenior-pm` | Broader PM scope — status reports feed into PM reporting |\n| `project-management\u002Fmeeting-analyzer` | Meeting insights can feed into 3P updates and status reports |\n| `project-management\u002Fconfluence-expert` | Publish comms as Confluence pages for permanent record |\n| `marketing-skill\u002Fcontent-production` | External comms — use for public-facing content, not internal |\n","# Internal Comms\n\n> Originally contributed by [maximcoding](https:\u002F\u002Fgithub.com\u002Fmaximcoding) — enhanced and integrated by the claude-skills team.\n\nWrite polished internal communications by loading the right reference file, gathering context, and outputting in the company's exact format.\n\n## Routing\n\nIdentify the communication type from the user's request, then read the matching reference file before writing anything:\n\n| Type | Trigger phrases | Reference file |\n|---|---|---|\n| **3P Update** | \"3P\", \"progress plans problems\", \"weekly team update\", \"what did we ship\" | `references\u002F3p-updates.md` |\n| **Newsletter** | \"newsletter\", \"company update\", \"weekly\u002Fmonthly roundup\", \"all-hands summary\" | `references\u002Fcompany-newsletter.md` |\n| **FAQ** | \"FAQ\", \"common questions\", \"what people are asking\", \"confusion around\" | `references\u002Ffaq-answers.md` |\n| **General** | anything internal that doesn't match above | `references\u002Fgeneral-comms.md` |\n\nIf the type is ambiguous, ask one clarifying question — don't guess.\n\n## Workflow\n\n1. **Read the reference file** for the matched type. Follow its formatting exactly.\n2. **Gather inputs.** Use available MCP tools (Slack, Gmail, Google Drive, Calendar) to pull real data. If no tools are connected, ask the user to provide bullet points or raw context.\n3. **Clarify scope.** Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.\n4. **Draft.** Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.\n5. **Present the draft** and ask if anything needs to be added, removed, or reworded.\n\n## Tone & Style (applies to all types)\n\n- Use \"we\" — you are part of the company.\n- Active voice, present tense for progress, future tense for plans.\n- Concise. Every sentence should carry information. Cut filler.\n- Include metrics and links wherever possible.\n- Professional but approachable — not corporate-speak.\n- Put the most important information first.\n\n## When tools are unavailable\n\nIf the user hasn't connected Slack, Gmail, Drive, or Calendar, don't stall. Ask them to paste or describe what they want covered. You're formatting and sharpening — that's still valuable. Mention which tools would improve future drafts so they can connect them later.\n\n---\n\n## Anti-Patterns\n\n| Anti-Pattern | Why It Fails | Better Approach |\n|---|---|---|\n| Writing updates without reading the reference template first | Output won't match company format — user has to reformat | Always load the matching reference file before drafting |\n| Inventing metrics or accomplishments | Internal comms must be factual — fabrication destroys trust | Only include data the user provided or MCP tools retrieved |\n| Using passive voice for accomplishments | \"The feature was shipped\" hides who did the work | \"Team X shipped the feature\" — active voice credits the team |\n| Writing walls of text for status updates | Leadership scans, doesn't read — key info gets buried | Lead with the headline, follow with 3-5 bullet points |\n| Sending without confirming audience | A team update reads differently from a company-wide newsletter | Always confirm: who will read this? |\n\n---\n\n## Related Skills\n\n| Skill | Relationship |\n|-------|-------------|\n| `project-management\u002Fsenior-pm` | Broader PM scope — status reports feed into PM reporting |\n| `project-management\u002Fmeeting-analyzer` | Meeting insights can feed into 3P updates and status reports |\n| `project-management\u002Fconfluence-expert` | Publish comms as Confluence pages for permanent record |\n| `marketing-skill\u002Fcontent-production` | External comms — use for public-facing content, not internal |\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fteam-communications",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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill team-communications",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill team-communications",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill team-communications","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fteam-communications\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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",[],[]]