[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73DSAGJF6TXF7PSDPTRHCCF":3,"skill-same:01M73DSAGJF6TXF7PSDPTRHCCF":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},"01M73DSAGJF6TXF7PSDPTRHCCF","messages-ops",null,"Evidence-first live messaging workflow for ECC. Use when the user wants to read texts or DMs, recover a recent one-time code, inspect a thread before replying, or prove which message source was actually checked.","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\u002Fmessages-ops\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: messages-ops\ndescription: Evidence-first live messaging workflow for ECC. Use when the user wants to read texts or DMs, recover a recent one-time code, inspect a thread before replying, or prove which message source was actually checked.\norigin: ECC\n---\n\n# Messages Ops\n\nUse this when the task is live-message retrieval: iMessage, DMs, recent one-time codes, or thread inspection before a follow-up.\n\nThis is not email work. If the dominant surface is a mailbox, use `email-ops`.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `email-ops` when the message task is really mailbox work\n- `connections-optimizer` when the DM thread belongs to outbound network work\n- `lead-intelligence` when the live thread should inform targeting or warm-path outreach\n- `knowledge-ops` when the thread contents need to be captured into durable context\n\n## When to Use\n\n- user says \"read my messages\", \"check texts\", \"look in DMs\", or \"find the code\"\n- the task depends on a live thread or a recent code delivered to a local messaging surface\n- the user wants proof of which source or thread was inspected\n\n## Guardrails\n\n- resolve the source first:\n  - local messages\n  - X \u002F social DM\n  - another browser-gated message surface\n- do not claim a thread was checked without naming the source\n- do not improvise raw database access if a checked helper or standard path exists\n- if auth or MFA blocks the surface, report the exact blocker\n\n## Workflow\n\n### 1. Resolve the exact thread\n\nBefore doing anything else, settle:\n\n- message surface\n- sender \u002F recipient \u002F service\n- time window\n- whether the task is retrieval, inspection, or prep for a reply\n\n### 2. Read before drafting\n\nIf the task may turn into an outbound follow-up:\n\n- read the latest inbound\n- identify the open loop\n- then hand off to the correct outbound skill if needed\n\n### 3. Handle codes as a focused retrieval task\n\nFor one-time codes:\n\n- search the recent local message window first\n- narrow by service or sender when possible\n- stop once the code is found or the focused search is exhausted\n\n### 4. Report exact evidence\n\nReturn:\n\n- source used\n- thread or sender when possible\n- time window\n- exact status:\n  - read\n  - code-found\n  - blocked\n  - awaiting reply draft\n\n## Output Format\n\n```text\nSOURCE\n- message surface\n- sender \u002F thread \u002F service\n\nRESULT\n- message summary or code\n- time window\n\nSTATUS\n- read \u002F code-found \u002F blocked \u002F awaiting reply draft\n```\n\n## Pitfalls\n\n- do not blur mailbox work and DM\u002Ftext work\n- do not claim retrieval without naming the source\n- do not burn time on broad searches when the ask is a recent-code lookup\n- do not keep retrying a blocked auth path without surfacing the blocker\n\n## Verification\n\n- the response names the message source\n- the response includes a sender, service, thread, or clear blocker\n- the final state is explicit and bounded\n","# Messages Ops\n\nUse this when the task is live-message retrieval: iMessage, DMs, recent one-time codes, or thread inspection before a follow-up.\n\nThis is not email work. If the dominant surface is a mailbox, use `email-ops`.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `email-ops` when the message task is really mailbox work\n- `connections-optimizer` when the DM thread belongs to outbound network work\n- `lead-intelligence` when the live thread should inform targeting or warm-path outreach\n- `knowledge-ops` when the thread contents need to be captured into durable context\n\n## When to Use\n\n- user says \"read my messages\", \"check texts\", \"look in DMs\", or \"find the code\"\n- the task depends on a live thread or a recent code delivered to a local messaging surface\n- the user wants proof of which source or thread was inspected\n\n## Guardrails\n\n- resolve the source first:\n  - local messages\n  - X \u002F social DM\n  - another browser-gated message surface\n- do not claim a thread was checked without naming the source\n- do not improvise raw database access if a checked helper or standard path exists\n- if auth or MFA blocks the surface, report the exact blocker\n\n## Workflow\n\n### 1. Resolve the exact thread\n\nBefore doing anything else, settle:\n\n- message surface\n- sender \u002F recipient \u002F service\n- time window\n- whether the task is retrieval, inspection, or prep for a reply\n\n### 2. Read before drafting\n\nIf the task may turn into an outbound follow-up:\n\n- read the latest inbound\n- identify the open loop\n- then hand off to the correct outbound skill if needed\n\n### 3. Handle codes as a focused retrieval task\n\nFor one-time codes:\n\n- search the recent local message window first\n- narrow by service or sender when possible\n- stop once the code is found or the focused search is exhausted\n\n### 4. Report exact evidence\n\nReturn:\n\n- source used\n- thread or sender when possible\n- time window\n- exact status:\n  - read\n  - code-found\n  - blocked\n  - awaiting reply draft\n\n## Output Format\n\n```text\nSOURCE\n- message surface\n- sender \u002F thread \u002F service\n\nRESULT\n- message summary or code\n- time window\n\nSTATUS\n- read \u002F code-found \u002F blocked \u002F awaiting reply draft\n```\n\n## Pitfalls\n\n- do not blur mailbox work and DM\u002Ftext work\n- do not claim retrieval without naming the source\n- do not burn time on broad searches when the ask is a recent-code lookup\n- do not keep retrying a blocked auth path without surfacing the blocker\n\n## Verification\n\n- the response names the message source\n- the response includes a sender, service, thread, or clear blocker\n- the final state is explicit and bounded\n",{"name":5,"origin":24,"description":7},"ECC","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fmessages-ops",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 messages-ops",{"tool":41,"command":42},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill messages-ops",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill messages-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fmessages-ops\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",[],[]]