[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CN63ADPN8MDM86DXM4MSZ1":3,"skill-same:01M6CN63ADPN8MDM86DXM4MSZ1":58},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6CN63ADPN8MDM86DXM4MSZ1","ops",null,"Track who owes what by when, and notice when the same process step keeps slipping. Writes append-only markdown cards under workspace\u002Fops\u002F — commitments, processes, blockers, slips — cross-linked by [[slug]] so a blocker resolves to the commitment it holds up and a slip resolves to the step that produced it. TRIGGER: any promise with an owner and a date, anything stuck waiting on a decision, a due date that moved, or a request for what is open\u002Foverdue\u002Frepeatedly slipping. SKIP: one-off notes with no owner and no date — those are memory, not commitments.","joshuamschultz\u002FArc","joshuamschultz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2312349?v=4","01M6CN5XFME1WP2XMKCZBH4MMG","Josh","01M6CN5XMCNJTZPB9HE6N2MD2R",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjoshuamschultz\u002FArc\u002Fblob\u002Fmain\u002Fblueprints\u002Fbusiness-ops\u002Fskills\u002Fops\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29],"memory","notes","open","markdown","decision","workspace","append","process","only","up","promise","2026-11-10 10:12:30",false,"---\nname: ops\ndescription: \"Track who owes what by when, and notice when the same process step keeps slipping. Writes append-only markdown cards under workspace\u002Fops\u002F — commitments, processes, blockers, slips — cross-linked by [[slug]] so a blocker resolves to the commitment it holds up and a slip resolves to the step that produced it. TRIGGER: any promise with an owner and a date, anything stuck waiting on a decision, a due date that moved, or a request for what is open\u002Foverdue\u002Frepeatedly slipping. SKIP: one-off notes with no owner and no date — those are memory, not commitments.\"\nversion: 2.0.0\n---\n\n## Files\n\n- `ops\u002Fcommitments\u002F\u003Cslug>.md` — one card per commitment.\n- `ops\u002Fprocesses\u002F\u003Cslug>.md` — one card per recurring process.\n- `ops\u002Fblockers\u002F\u003Cslug>.md` — one card per blocker.\n- `ops\u002Fslips\u002Fslips.md` — the single running slip log.\n\nAll paths are relative to the agent's own workspace, written with the ordinary\nfile tools (`read`, `write`, `ls`, `grep`). There is no ops tool to call and none\nis needed — this is the agent's own workspace.\n\n## Contract\n\n1. Every commitment, process, blocker, and slip lands on its card at\n   `ops\u002F\u003Ckind>\u002F\u003Cslug>.md`.\n2. Cards are **appended to, never rewritten**: read, add the entry at the end,\n   write the whole file back.\n3. A new card starts with exactly this header and nothing else:\n\n   ```\n   # \u003CTitle>\n\n   - slug: \u003Cslug>\n   - type: \u003Ckind>\n   ```\n\n4. Each entry is a UTC timestamp heading followed by `- key: value` lines,\n   omitting every field with no value.\n5. References to another card are written `[[slug]]`, never a bare name.\n6. **Blocked and late are recorded as different states.** A commitment past due\n   is `status: open` and overdue; one waiting on someone else is a blocker card\n   with a named `decider`.\n7. A slip appends to BOTH the commitment's card and `ops\u002Fslips\u002Fslips.md`.\n\n## Knowledge\n\n- **Blocked and late need opposite responses.** Late needs a push to the owner;\n  blocked needs a decision from somebody else. Collapsing them into \"not done\" is\n  how a blocker sits for three weeks while someone politely re-pings the person\n  who was never the obstacle.\n- **A slip is data, not an apology.** Logging it against the *process step* is\n  what turns three slips into a visible defect instead of three bad weeks.\n- **The slug is the identity.** Lowercase, non-alphanumeric runs → `-`, strip\n  ends. The same commitment must always produce the same slug, or its history\n  forks and neither half is true.\n- **Get the timestamp from the clock**: run `date -u +'%Y-%m-%d %H:%M'` and use\n  exactly what it returns. The prompt carries the date but not the time, so a\n  remembered timestamp lands at `00:00`.\n- A commitment with no `due` cannot be overdue and cannot be chased. Record it,\n  and say that the date is missing.\n- Never invent an owner or a date. An empty field is honest.\n\n### Fields by kind\n\n| Kind | Fields |\n|---|---|\n| `commitments` | `commitment`, `owner`, `due`, `process` (link), `status` (default `open`) |\n| `processes` | `name`, `owner`, `cadence`, `steps`, `handoffs` |\n| `blockers` | `blocker`, `blocked_on`, `decider`, `since` (default today), `commitment` (link), `status: blocked` |\n| `slips` | `slipped`, `process` (link), `step`, `reason`, `new_due`, `status: slipped` |\n\nFree-text context goes on a final `- note:` line.\n\n## Steps\n\n**To log a commitment, process, or blocker:**\n\n1. Run `date -u +'%Y-%m-%d %H:%M'`.\n2. Derive the slug from the name.\n3. `read` `ops\u002F\u003Ckind>\u002F\u003Cslug>.md`; if absent, start from the header block.\n4. Append a blank line, the `## \u003Ctimestamp>` heading, and one `- key: value` line\n   per non-empty field, then `- note:` if there is context.\n5. `write` the whole file back.\n6. Reply in one line naming what was logged and its owner\u002Fdue.\n\n**To log a slip:**\n\n1. Append the slip fields to `ops\u002Fcommitments\u002F\u003Ccommitment-slug>.md`.\n2. Append the same fields to `ops\u002Fslips\u002Fslips.md`.\n3. Reply naming the new due date and the process step that produced the slip.\n\n**To report status (open commitments):**\n\n1. `ls` `ops\u002Fcommitments\u002F`, `read` each card, take the **last** value of each field.\n2. Drop anything whose latest `status` is `done`.\n3. Sort overdue first (by `due`, earliest first), then dated, then undated.\n4. Group by `owner`, and mark any commitment that has a blocker card referencing\n   it with `⛔ blocked on \u003Cdecider>`.\n\n**To find slip patterns:**\n\n1. `read` `ops\u002Fslips\u002Fslips.md`.\n2. Count entries per `process` + `step` pair.\n3. Report every pair at or above the threshold (default 3), most frequent first,\n   as a defect in that step — not as bad luck.\n\n## Red Flags & Rationalizations\n\n| Thought | Reality |\n|---|---|\n| \"It's late, I'll just mark it not done.\" | Late and blocked need opposite actions. Log a blocker with its decider. |\n| \"I'll rewrite the card so it reads cleanly.\" | That deletes the history that makes slips visible. Append. |\n| \"The slip is obvious, no need to log it.\" | Three unlogged slips look like bad luck; three logged ones name a broken step. |\n| \"No due date was given, I'll estimate one.\" | An invented date becomes someone's commitment. Leave it empty and say so. |\n| \"I know roughly what time it is.\" | You know the date, not the time. Run `date -u` or the entry lands at 00:00. |\n| \"Status should show the first value I find.\" | Cards are append-only; the first is the oldest. Take the last. |\n\n## Validation\n\nA log is correct when:\n\n- [ ] The card exists at `ops\u002F\u003Ckind>\u002F\u003Cslug>.md` with the exact header block.\n- [ ] Every prior entry is present, unmodified.\n- [ ] The `## YYYY-MM-DD HH:MM` heading came from `date -u`, not `00:00`.\n- [ ] Blocked items are blocker cards with a named `decider`, not overdue commitments.\n- [ ] A slip appears in BOTH the commitment card and `ops\u002Fslips\u002Fslips.md`.\n\nA status report is correct when every open commitment appears exactly once, with\nits latest values, overdue first, and blockers called out.\n\n## Examples\n\n**A commitment:**\n\n> \"Dana owes the vendor security review by the 20th, part of the onboarding process.\"\n\nAppends to `ops\u002Fcommitments\u002Fvendor-security-review.md`:\n\n```\n\n## 2026-08-14 17:20\n- commitment: Vendor security review\n- owner: Dana\n- due: 2026-08-20\n- process: [[vendor-onboarding]]\n- status: open\n```\n\nReply: `Logged commitment 'Vendor security review' — Dana, due 2026-08-20`\n\n**A blocker (not an overdue commitment):**\n\nReply: `Logged blocker 'Vendor security review' — blocked on legal sign-off, decider: Priya (since 2026-08-14)`\n\n**A slip pattern:**\n\n```\nRepeated slips (threshold 3):\n- vendor-onboarding \u002F security review: 4 slips — this step is a defect, not bad luck\n```\n","## Files\n\n- `ops\u002Fcommitments\u002F\u003Cslug>.md` — one card per commitment.\n- `ops\u002Fprocesses\u002F\u003Cslug>.md` — one card per recurring process.\n- `ops\u002Fblockers\u002F\u003Cslug>.md` — one card per blocker.\n- `ops\u002Fslips\u002Fslips.md` — the single running slip log.\n\nAll paths are relative to the agent's own workspace, written with the ordinary\nfile tools (`read`, `write`, `ls`, `grep`). There is no ops tool to call and none\nis needed — this is the agent's own workspace.\n\n## Contract\n\n1. Every commitment, process, blocker, and slip lands on its card at\n   `ops\u002F\u003Ckind>\u002F\u003Cslug>.md`.\n2. Cards are **appended to, never rewritten**: read, add the entry at the end,\n   write the whole file back.\n3. A new card starts with exactly this header and nothing else:\n\n   ```\n   # \u003CTitle>\n\n   - slug: \u003Cslug>\n   - type: \u003Ckind>\n   ```\n\n4. Each entry is a UTC timestamp heading followed by `- key: value` lines,\n   omitting every field with no value.\n5. References to another card are written `[[slug]]`, never a bare name.\n6. **Blocked and late are recorded as different states.** A commitment past due\n   is `status: open` and overdue; one waiting on someone else is a blocker card\n   with a named `decider`.\n7. A slip appends to BOTH the commitment's card and `ops\u002Fslips\u002Fslips.md`.\n\n## Knowledge\n\n- **Blocked and late need opposite responses.** Late needs a push to the owner;\n  blocked needs a decision from somebody else. Collapsing them into \"not done\" is\n  how a blocker sits for three weeks while someone politely re-pings the person\n  who was never the obstacle.\n- **A slip is data, not an apology.** Logging it against the *process step* is\n  what turns three slips into a visible defect instead of three bad weeks.\n- **The slug is the identity.** Lowercase, non-alphanumeric runs → `-`, strip\n  ends. The same commitment must always produce the same slug, or its history\n  forks and neither half is true.\n- **Get the timestamp from the clock**: run `date -u +'%Y-%m-%d %H:%M'` and use\n  exactly what it returns. The prompt carries the date but not the time, so a\n  remembered timestamp lands at `00:00`.\n- A commitment with no `due` cannot be overdue and cannot be chased. Record it,\n  and say that the date is missing.\n- Never invent an owner or a date. An empty field is honest.\n\n### Fields by kind\n\n| Kind | Fields |\n|---|---|\n| `commitments` | `commitment`, `owner`, `due`, `process` (link), `status` (default `open`) |\n| `processes` | `name`, `owner`, `cadence`, `steps`, `handoffs` |\n| `blockers` | `blocker`, `blocked_on`, `decider`, `since` (default today), `commitment` (link), `status: blocked` |\n| `slips` | `slipped`, `process` (link), `step`, `reason`, `new_due`, `status: slipped` |\n\nFree-text context goes on a final `- note:` line.\n\n## Steps\n\n**To log a commitment, process, or blocker:**\n\n1. Run `date -u +'%Y-%m-%d %H:%M'`.\n2. Derive the slug from the name.\n3. `read` `ops\u002F\u003Ckind>\u002F\u003Cslug>.md`; if absent, start from the header block.\n4. Append a blank line, the `## \u003Ctimestamp>` heading, and one `- key: value` line\n   per non-empty field, then `- note:` if there is context.\n5. `write` the whole file back.\n6. Reply in one line naming what was logged and its owner\u002Fdue.\n\n**To log a slip:**\n\n1. Append the slip fields to `ops\u002Fcommitments\u002F\u003Ccommitment-slug>.md`.\n2. Append the same fields to `ops\u002Fslips\u002Fslips.md`.\n3. Reply naming the new due date and the process step that produced the slip.\n\n**To report status (open commitments):**\n\n1. `ls` `ops\u002Fcommitments\u002F`, `read` each card, take the **last** value of each field.\n2. Drop anything whose latest `status` is `done`.\n3. Sort overdue first (by `due`, earliest first), then dated, then undated.\n4. Group by `owner`, and mark any commitment that has a blocker card referencing\n   it with `⛔ blocked on \u003Cdecider>`.\n\n**To find slip patterns:**\n\n1. `read` `ops\u002Fslips\u002Fslips.md`.\n2. Count entries per `process` + `step` pair.\n3. Report every pair at or above the threshold (default 3), most frequent first,\n   as a defect in that step — not as bad luck.\n\n## Red Flags & Rationalizations\n\n| Thought | Reality |\n|---|---|\n| \"It's late, I'll just mark it not done.\" | Late and blocked need opposite actions. Log a blocker with its decider. |\n| \"I'll rewrite the card so it reads cleanly.\" | That deletes the history that makes slips visible. Append. |\n| \"The slip is obvious, no need to log it.\" | Three unlogged slips look like bad luck; three logged ones name a broken step. |\n| \"No due date was given, I'll estimate one.\" | An invented date becomes someone's commitment. Leave it empty and say so. |\n| \"I know roughly what time it is.\" | You know the date, not the time. Run `date -u` or the entry lands at 00:00. |\n| \"Status should show the first value I find.\" | Cards are append-only; the first is the oldest. Take the last. |\n\n## Validation\n\nA log is correct when:\n\n- [ ] The card exists at `ops\u002F\u003Ckind>\u002F\u003Cslug>.md` with the exact header block.\n- [ ] Every prior entry is present, unmodified.\n- [ ] The `## YYYY-MM-DD HH:MM` heading came from `date -u`, not `00:00`.\n- [ ] Blocked items are blocker cards with a named `decider`, not overdue commitments.\n- [ ] A slip appears in BOTH the commitment card and `ops\u002Fslips\u002Fslips.md`.\n\nA status report is correct when every open commitment appears exactly once, with\nits latest values, overdue first, and blockers called out.\n\n## Examples\n\n**A commitment:**\n\n> \"Dana owes the vendor security review by the 20th, part of the onboarding process.\"\n\nAppends to `ops\u002Fcommitments\u002Fvendor-security-review.md`:\n\n```\n\n## 2026-08-14 17:20\n- commitment: Vendor security review\n- owner: Dana\n- due: 2026-08-20\n- process: [[vendor-onboarding]]\n- status: open\n```\n\nReply: `Logged commitment 'Vendor security review' — Dana, due 2026-08-20`\n\n**A blocker (not an overdue commitment):**\n\nReply: `Logged blocker 'Vendor security review' — blocked on legal sign-off, decider: Priya (since 2026-08-14)`\n\n**A slip pattern:**\n\n```\nRepeated slips (threshold 3):\n- vendor-onboarding \u002F security review: 4 slips — this step is a defect, not bad luck\n```\n",{"name":5,"version":35,"description":7},"2.0.0","main","e2fb5cfd858fb29298ab468e61a273f1e372b0e7","blueprints\u002Fbusiness-ops\u002Fskills\u002Fops",0,"https:\u002F\u002Fgithub.com\u002Fjoshuamschultz\u002FArc","https:\u002F\u002Fgithub.com\u002Fjoshuamschultz","https:\u002F\u002Fjoshuaschultz.com","2026-10-22 08:51:07",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add joshuamschultz\u002FArc --skill ops",{"tool":50,"command":51},"bunx","bunx skills add joshuamschultz\u002FArc --skill ops",{"tool":53,"command":54},"pnpm","pnpm dlx skills add joshuamschultz\u002FArc --skill ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjoshuamschultz\u002FArc\u002Fblob\u002Fmain\u002Fblueprints\u002Fbusiness-ops\u002Fskills\u002Fops\u002FSKILL.md",true,[],[59,69,99,118,127,140],{"skillNo":60,"name":20,"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":30},"01M6CN91Q5XSKA66KDKFV9BRTQ","Read a note back with the notes_echo tool.","https:\u002F\u002Fgithub.com\u002Fjoshuamschultz\u002FArc\u002Fblob\u002Fmain\u002Fpackages\u002Farcagent\u002Ftests\u002Ffixtures\u002Fnotes_connector\u002Fskills\u002Fnotes\u002FSKILL.md",[],[20,65,66,67,68],"back","tool","read","Echo",{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":80,"publishedAt":30},"01M6CN8Z0BXKCQEJGJG21DFPA7","workflow-builder","Turn a repeatable business process described in conversation into a named, validated ArcFlow workflow draft.","https:\u002F\u002Fgithub.com\u002Fjoshuamschultz\u002FArc\u002Fblob\u002Fmain\u002Fpackages\u002Farcagent\u002Fsrc\u002Farcagent\u002Fbuiltins\u002Fcapabilities\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[81,82,83,84,85,86,87,88,89,90,91,92,26,93,94,95,96,97,98],"builder","workflow builder","workflow","create","run","automate this","SET","automate","node","edit","list","business","channel","remove","files","build","conversation","do",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":30},"01M6CN8VZT2YXB8EFJRHSCZ735","update-tool","Update an existing @tool source file in workspace\u002Fcapabilities\u002F, bumping its semver per major\u002Fminor\u002Fpatch.","https:\u002F\u002Fgithub.com\u002Fjoshuamschultz\u002FArc\u002Fblob\u002Fmain\u002Fpackages\u002Farcagent\u002Fsrc\u002Farcagent\u002Fbuiltins\u002Fcapabilities\u002Fskills\u002Fupdate-tool\u002FSKILL.md",[],[106,107,66,108,109,110,111,112,113,67,114,115,116,117,24],"update tool","update","bump","bug","behavior","patch","version","fix","change","semver","capabilities","file",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":125,"publishedAt":30},"01M6CN8SJRCCV05HMF91ZNAK8Z","update-skill","Update an existing skill's SKILL.md body in workspace\u002Fcapabilities\u002Fskills\u002F, bumping its frontmatter semver.","https:\u002F\u002Fgithub.com\u002Fjoshuamschultz\u002FArc\u002Fblob\u002Fmain\u002Fpackages\u002Farcagent\u002Fsrc\u002Farcagent\u002Fbuiltins\u002Fcapabilities\u002Fskills\u002Fupdate-skill\u002FSKILL.md",[124],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[107,126,115,116,24,67,113,112,108],"update skill",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":30},"01M6CN8PRNV3S8D4BZN9EYHWVZ","create-tool","Author a new @tool-decorated Python file in the agent workspace, validate it, and register it via reload().","https:\u002F\u002Fgithub.com\u002Fjoshuamschultz\u002FArc\u002Fblob\u002Fmain\u002Fpackages\u002Farcagent\u002Fsrc\u002Farcagent\u002Fbuiltins\u002Fcapabilities\u002Fskills\u002Fcreate-tool\u002FSKILL.md",[],[134,66,84,135,136,137,117,138,24,67,139,96],"create tool","agent workspace","python","validate","Bash","write",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":30},"01M6CN8M1G6VJPG9KQN9CA04BZ","create-skill","Scaffold a new skill folder under workspace\u002Fcapabilities\u002Fskills\u002F with frontmatter and the seven required sections.","https:\u002F\u002Fgithub.com\u002Fjoshuamschultz\u002FArc\u002Fblob\u002Fmain\u002Fpackages\u002Farcagent\u002Fsrc\u002Farcagent\u002Fbuiltins\u002Fcapabilities\u002Fskills\u002Fcreate-skill\u002FSKILL.md",[146],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[84,148,83,149,116,150,24,151,67,139,90,152,153],"create skill","scaffold","write a skill","capture","document","new skill"]