[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73A84FKBNEPB7NZA6BYBFRP":3,"skill-same:01M73A84FKBNEPB7NZA6BYBFRP":49},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M73A84FKBNEPB7NZA6BYBFRP","crosspost",null,"Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fcrosspost\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: crosspost\ndescription: Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.\norigin: ECC\n---\n\n# Crosspost\n\nDistribute content across platforms without turning it into the same fake post in four costumes.\n\n## When to Activate\n\n- the user wants to publish the same underlying idea across multiple platforms\n- a launch, update, release, or essay needs platform-specific versions\n- the user says \"crosspost\", \"post this everywhere\", or \"adapt this for X and LinkedIn\"\n\n## Core Rules\n\n1. Do not publish identical copy across platforms.\n2. Preserve the author's voice across platforms.\n3. Adapt for constraints, not stereotypes.\n4. One post should still be about one thing.\n5. Do not invent a CTA, question, or moral if the source did not earn one.\n\n## Workflow\n\n### Step 1: Start with the Primary Version\n\nPick the strongest source version first:\n- the original X post\n- the original article\n- the launch note\n- the thread\n- the memo or changelog\n\nUse `content-engine` first if the source still needs voice shaping.\n\n### Step 2: Capture the Voice Fingerprint\n\nRun `brand-voice` first if the source voice is not already captured in the current session.\n\nReuse the resulting `VOICE PROFILE` directly.\nDo not build a second ad hoc voice checklist here unless the user explicitly wants a fresh override for this campaign.\n\n### Step 3: Adapt by Platform Constraint\n\n### X\n\n- keep it compressed\n- lead with the sharpest claim or artifact\n- use a thread only when a single post would collapse the argument\n- avoid hashtags and generic filler\n\n### LinkedIn\n\n- add only the context needed for people outside the niche\n- do not turn it into a fake founder-reflection post\n- do not add a closing question just because it is LinkedIn\n- do not force a polished \"professional tone\" if the author is naturally sharper\n\n### Threads\n\n- keep it readable and direct\n- do not write fake hyper-casual creator copy\n- do not paste the LinkedIn version and shorten it\n\n### Bluesky\n\n- keep it concise\n- preserve the author's cadence\n- do not rely on hashtags or feed-gaming language\n\n## Posting Order\n\nDefault:\n1. post the strongest native version first\n2. adapt for the secondary platforms\n3. stagger timing only if the user wants sequencing help\n\nDo not add cross-platform references unless useful. Most of the time, the post should stand on its own.\n\n## Banned Patterns\n\nDelete and rewrite any of these:\n- \"Excited to share\"\n- \"Here's what I learned\"\n- \"What do you think?\"\n- \"link in bio\" unless that is literally true\n- generic \"professional takeaway\" paragraphs that were not in the source\n\n## Output Format\n\nReturn:\n- the primary platform version\n- adapted variants for each requested platform\n- a short note on what changed and why\n- any publishing constraint the user still needs to resolve\n\n## Quality Gate\n\nBefore delivering:\n- each version reads like the same author under different constraints\n- no platform version feels padded or sanitized\n- no copy is duplicated verbatim across platforms\n- any extra context added for LinkedIn or newsletter use is actually necessary\n\n## Related Skills\n\n- `brand-voice` for reusable source-derived voice capture\n- `content-engine` for voice capture and source shaping\n- `x-api` for X publishing workflows\n","# Crosspost\n\nDistribute content across platforms without turning it into the same fake post in four costumes.\n\n## When to Activate\n\n- the user wants to publish the same underlying idea across multiple platforms\n- a launch, update, release, or essay needs platform-specific versions\n- the user says \"crosspost\", \"post this everywhere\", or \"adapt this for X and LinkedIn\"\n\n## Core Rules\n\n1. Do not publish identical copy across platforms.\n2. Preserve the author's voice across platforms.\n3. Adapt for constraints, not stereotypes.\n4. One post should still be about one thing.\n5. Do not invent a CTA, question, or moral if the source did not earn one.\n\n## Workflow\n\n### Step 1: Start with the Primary Version\n\nPick the strongest source version first:\n- the original X post\n- the original article\n- the launch note\n- the thread\n- the memo or changelog\n\nUse `content-engine` first if the source still needs voice shaping.\n\n### Step 2: Capture the Voice Fingerprint\n\nRun `brand-voice` first if the source voice is not already captured in the current session.\n\nReuse the resulting `VOICE PROFILE` directly.\nDo not build a second ad hoc voice checklist here unless the user explicitly wants a fresh override for this campaign.\n\n### Step 3: Adapt by Platform Constraint\n\n### X\n\n- keep it compressed\n- lead with the sharpest claim or artifact\n- use a thread only when a single post would collapse the argument\n- avoid hashtags and generic filler\n\n### LinkedIn\n\n- add only the context needed for people outside the niche\n- do not turn it into a fake founder-reflection post\n- do not add a closing question just because it is LinkedIn\n- do not force a polished \"professional tone\" if the author is naturally sharper\n\n### Threads\n\n- keep it readable and direct\n- do not write fake hyper-casual creator copy\n- do not paste the LinkedIn version and shorten it\n\n### Bluesky\n\n- keep it concise\n- preserve the author's cadence\n- do not rely on hashtags or feed-gaming language\n\n## Posting Order\n\nDefault:\n1. post the strongest native version first\n2. adapt for the secondary platforms\n3. stagger timing only if the user wants sequencing help\n\nDo not add cross-platform references unless useful. Most of the time, the post should stand on its own.\n\n## Banned Patterns\n\nDelete and rewrite any of these:\n- \"Excited to share\"\n- \"Here's what I learned\"\n- \"What do you think?\"\n- \"link in bio\" unless that is literally true\n- generic \"professional takeaway\" paragraphs that were not in the source\n\n## Output Format\n\nReturn:\n- the primary platform version\n- adapted variants for each requested platform\n- a short note on what changed and why\n- any publishing constraint the user still needs to resolve\n\n## Quality Gate\n\nBefore delivering:\n- each version reads like the same author under different constraints\n- no platform version feels padded or sanitized\n- no copy is duplicated verbatim across platforms\n- any extra context added for LinkedIn or newsletter use is actually necessary\n\n## Related Skills\n\n- `brand-voice` for reusable source-derived voice capture\n- `content-engine` for voice capture and source shaping\n- `x-api` for X publishing workflows\n",{"name":5,"origin":24,"description":7},"ECC","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fcrosspost",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill crosspost",{"tool":41,"command":42},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill crosspost",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill crosspost","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fcrosspost\u002FSKILL.md",true,[],[50,58,65,73,81,89],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"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":92,"categories":93,"keywords":94,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]