[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70GFYSA5R51X9JWWR0H7S0S":3,"skill-same:01M70GFYSA5R51X9JWWR0H7S0S":78},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M70GFYSA5R51X9JWWR0H7S0S","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.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fmessages-ops\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"messages ops","ops","messages","first","thread","use","prove","for","evidence","source","live","read","message","code","workflow","when","time","inspect","messaging","which","2026-11-10 10:12:30",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.\nmetadata:\n  origin: 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,"metadata":54,"description":7},{"origin":55},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fmessages-ops",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill messages-ops",{"tool":70,"command":71},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill messages-ops",{"tool":73,"command":74},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill messages-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fmessages-ops\u002FSKILL.md",true,[],[79,87,95,102,109,116],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":94},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":94},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":94},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":94},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":94},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]