[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WX9QDGKMC5TY9YDJFCJHCB":3,"skill-same:01M6WX9QDGKMC5TY9YDJFCJHCB":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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":14,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6WX9QDGKMC5TY9YDJFCJHCB","email-drafter",null,"Drafts clear, professional emails ready to copy and paste — from a brief description of the situation, audience, and intent. Use when asked to write, draft, or compose an email, reply to a message, or suggest how to phrase something professionally.","projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.10.0\u002Fcontext\u002Fskills\u002Fproduct\u002Femail-drafter\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"email","email drafter","when","product","v1","paste","drafts","professional","how to","emails","draft","message","intent","compose","ready","use","write","work","how","brief","2026-11-10 10:12:30",false,"---\nname: email-drafter\ndescription: |\n  Drafts clear, professional emails ready to copy and paste — from a brief description of the situation, audience, and intent. Use when asked to write, draft, or compose an email, reply to a message, or suggest how to phrase something professionally.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv1\n    id: SKILL-email-drafter\n    version: \"1.0.0\"\n    created: 2026-04-08T00:00:00Z\n    category: product\n    layer: 2\n---\n\n# Email Drafter\n\n## Intro\n\nA good email delivers one clear message, respects the reader's time,\nand makes the desired next action obvious. Before writing, identify\nthe situation, the audience's relationship and context, and the single\nthing you need the recipient to do or understand. Then write the\nshortest email that achieves that goal.\n\n## Overview\n\n### Before you write — gather the inputs\n\nAsk for (or infer) these before drafting:\n\n1. **Situation** — what happened or what is needed\n2. **Recipient** — their role, relationship (colleague, client, manager,\n   stranger), and level of context about the topic\n3. **Intent** — the one thing the email must accomplish (inform, request,\n   apologize, confirm, decline, follow up)\n4. **Tone** — formal, professional-but-warm, casual, urgent\n5. **Any constraints** — deadline, prior emails in the thread, sensitive\n   content to avoid\n\nIf the user has given enough context, draft immediately. Do not ask\nfor information that can be reasonably inferred.\n\n### Email types and their patterns\n\n**Request**\n> Subject: [Action needed] — [Topic] by [Date]  \n> Open with context (1 sentence). State the ask directly. Give\n> rationale in 1-2 sentences. Specify the deadline and format of\n> response needed. Close with thanks or next step.\n\n**Status update**\n> Subject: [Project] update — [Date\u002FPhase]  \n> Open with the one-line headline (good news, concern, or neutral).\n> Bullet the key points (3-5 max). State what happens next and who\n> owns it. Close with \"let me know if you have questions.\"\n\n**Follow-up \u002F nudge**\n> Subject: Re: [original subject]  \n> Acknowledge the prior exchange in one line. Restate the ask\n> briefly. If there is a deadline, name it. Keep the tone light\n> unless the situation is urgent.\n\n**Apology \u002F acknowledgment**\n> Subject: [Topic] — apology \u002F correction  \n> Lead with the apology, not context. Be specific about what went\n> wrong. State what has changed or will change. No overexplaining.\n\n**Decline \u002F boundary**\n> Subject: Re: [original subject]  \n> Acknowledge the ask. State the decline directly. Give a brief,\n> honest reason (optional). Offer an alternative if one exists.\n> Close warmly.\n\n**Announcement**\n> Subject: [What's changing] — effective [Date]  \n> Open with the what and when. Explain why in 2-3 sentences. State\n> what the recipient needs to do (if anything). Include a contact\n> for questions.\n\n### Subject line rules\n\n- Start with the type if actionable: `[Action needed]`, `[FYI]`,\n  `[Decision required]`, `[Update]`\n- 6-10 words maximum — enough to survive a mobile inbox preview\n- Be specific: `Q1 budget review — please approve by Friday` beats\n  `Budget question`\n- Never leave subject blank\n\n### Formatting and length\n\n- **One screen** — most emails should fit without scrolling\n- **One paragraph per idea** — no walls of text\n- **Bullets for lists of 3+** — easier to scan than prose\n- **No bold\u002Fitalic unless signaling urgency** — decorative formatting\n  reads as noise in plain-text clients\n- **Call to action at the end** — end with what you want: \"Please\n  reply by Thursday\" or \"No response needed — just keeping you in\n  the loop\"\n- **Signature** — include name and title only; leave phone\u002Flinks for\n  formal external emails\n\n### Tone calibration\n\n| Relationship | Opening | Closing |\n|---|---|---|\n| Close colleague | Hi [first name], | Thanks \u002F Cheers |\n| Professional peer | Hi [first name], | Best \u002F Thanks |\n| Client \u002F external | Dear [Mr.\u002FMs. Last] \u002F Hi [First], | Best regards \u002F Thank you |\n| Executive \u002F senior | Hi [First], | Thanks \u002F Best |\n| Unknown \u002F cold | Dear [First Last], | Best regards |\n\nMatch the energy the recipient uses in prior threads. When in doubt,\none step more formal than you think you need.\n\n### Draft output format\n\nProduce the email as copy-paste ready text:\n\n```\nSubject: [Subject line]\n\n[Salutation],\n\n[Body — 1-4 paragraphs, or bullets where appropriate]\n\n[Call to action or closing line]\n\n[Sign-off],\n[Name]\n[Title if applicable]\n```\n\nDo not wrap in code blocks or markdown unless the user explicitly\nwants it formatted that way.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Writing a long email when the intent can be stated in two sentences.** Longer emails get less attention, not more. Before finalizing, ask: \"what is the single thing this email must accomplish?\" Then cut everything that doesn't serve that goal. If the email needs more than one screen, it probably needs to be a document with a covering email instead.\n- **Burying the ask at the bottom.** Readers scan emails from the top. The request, decision, or key fact must appear in the first or second sentence — not after two paragraphs of background. Move context after the ask, not before.\n- **Drafting without knowing the audience's relationship and context.** An email to a close colleague who knows the project needs no preamble; the same email to an external stakeholder needs a one-sentence orientation. Always check the recipient type before setting the tone and level of detail.\n- **Using passive voice to soften bad news.** \"Mistakes were made\" and \"the deadline was missed\" avoid accountability. Professional emails about problems use active voice and first-person ownership: \"We missed the deadline\" and \"I should have flagged this earlier.\" Passive voice reads as evasive.\n- **Copying too many people.** Every extra recipient in CC adds noise and diffuses accountability. CC only people who need the information to do their job. Use BCC only for large announcements where reply-all chaos would be a problem.\n- **Treating the subject line as an afterthought.** Subjects determine whether the email is opened and found later. A vague subject (\"Question\", \"Hi\", \"Follow-up\") fails both jobs. Write the subject last, after the body is clear, so it accurately reflects the content.\n- **Sending the first draft without a read-through.** The most common email errors — wrong name, forgotten attachment, accidentally harsh phrasing, missing call to action — are caught in a single read-aloud pass. Always read the draft once from the recipient's perspective before finalizing.\n\n## Full reference\n\n### Reply vs. new thread\n\nReply to existing threads when the email is clearly part of an\nongoing conversation. Start a new thread when:\n- The topic has substantially shifted from the original subject\n- The original thread is long (>10 messages) and the new ask is\n  distinct\n- The recipient group is different from the original\n\nWhen replying, trim the quoted thread to the last 1-2 relevant\nmessages — full thread quoting adds length without value.\n\n### Sensitive topics\n\nApologies, performance feedback, salary discussions, and conflict\nresolution almost always land better in person or on video.\nIf the email must be written:\n- Lead with empathy, not defensiveness\n- Use \"I\" statements, not \"you\" statements\n- Propose a call to continue the conversation\n- Never send an angry email immediately — draft it, save it, review\n  after an hour\n\n### Templates for common scenarios\n\n**Meeting request:**\n> Subject: [Topic] — 30-min meeting request  \n> Hi [Name],  \n> I'd like to connect about [topic] — [1 sentence on why it matters\n> now]. Would you have 30 minutes available [proposed window]? Happy\n> to adjust if that doesn't work.  \n> Best, [Name]\n\n**Resignation:**\n> Subject: Resignation — [Name], effective [Date]  \n> Dear [Manager],  \n> I am writing to formally resign from my position as [title],\n> effective [date].  \n> [1-2 sentences of appreciation.]  \n> I am happy to assist with the transition in any way that would\n> be helpful.  \n> Thank you for [specific thing].  \n> Best regards, [Name]\n\n**Reference request:**\n> Subject: Reference request — [Your name], [Role] at [Company]  \n> Hi [Name],  \n> I'm applying for [role] at [company] and would be grateful if\n> you'd be willing to serve as a reference. The role is [1 line].  \n> Would you be comfortable speaking to my work on [specific\n> project\u002Fskill]? If so, they may contact you at [recruiter email]\n> in the coming [timeframe].  \n> Please let me know if you have any questions or if you'd prefer\n> not to — either is completely fine.  \n> Many thanks, [Name]\n","# Email Drafter\n\n## Intro\n\nA good email delivers one clear message, respects the reader's time,\nand makes the desired next action obvious. Before writing, identify\nthe situation, the audience's relationship and context, and the single\nthing you need the recipient to do or understand. Then write the\nshortest email that achieves that goal.\n\n## Overview\n\n### Before you write — gather the inputs\n\nAsk for (or infer) these before drafting:\n\n1. **Situation** — what happened or what is needed\n2. **Recipient** — their role, relationship (colleague, client, manager,\n   stranger), and level of context about the topic\n3. **Intent** — the one thing the email must accomplish (inform, request,\n   apologize, confirm, decline, follow up)\n4. **Tone** — formal, professional-but-warm, casual, urgent\n5. **Any constraints** — deadline, prior emails in the thread, sensitive\n   content to avoid\n\nIf the user has given enough context, draft immediately. Do not ask\nfor information that can be reasonably inferred.\n\n### Email types and their patterns\n\n**Request**\n> Subject: [Action needed] — [Topic] by [Date]  \n> Open with context (1 sentence). State the ask directly. Give\n> rationale in 1-2 sentences. Specify the deadline and format of\n> response needed. Close with thanks or next step.\n\n**Status update**\n> Subject: [Project] update — [Date\u002FPhase]  \n> Open with the one-line headline (good news, concern, or neutral).\n> Bullet the key points (3-5 max). State what happens next and who\n> owns it. Close with \"let me know if you have questions.\"\n\n**Follow-up \u002F nudge**\n> Subject: Re: [original subject]  \n> Acknowledge the prior exchange in one line. Restate the ask\n> briefly. If there is a deadline, name it. Keep the tone light\n> unless the situation is urgent.\n\n**Apology \u002F acknowledgment**\n> Subject: [Topic] — apology \u002F correction  \n> Lead with the apology, not context. Be specific about what went\n> wrong. State what has changed or will change. No overexplaining.\n\n**Decline \u002F boundary**\n> Subject: Re: [original subject]  \n> Acknowledge the ask. State the decline directly. Give a brief,\n> honest reason (optional). Offer an alternative if one exists.\n> Close warmly.\n\n**Announcement**\n> Subject: [What's changing] — effective [Date]  \n> Open with the what and when. Explain why in 2-3 sentences. State\n> what the recipient needs to do (if anything). Include a contact\n> for questions.\n\n### Subject line rules\n\n- Start with the type if actionable: `[Action needed]`, `[FYI]`,\n  `[Decision required]`, `[Update]`\n- 6-10 words maximum — enough to survive a mobile inbox preview\n- Be specific: `Q1 budget review — please approve by Friday` beats\n  `Budget question`\n- Never leave subject blank\n\n### Formatting and length\n\n- **One screen** — most emails should fit without scrolling\n- **One paragraph per idea** — no walls of text\n- **Bullets for lists of 3+** — easier to scan than prose\n- **No bold\u002Fitalic unless signaling urgency** — decorative formatting\n  reads as noise in plain-text clients\n- **Call to action at the end** — end with what you want: \"Please\n  reply by Thursday\" or \"No response needed — just keeping you in\n  the loop\"\n- **Signature** — include name and title only; leave phone\u002Flinks for\n  formal external emails\n\n### Tone calibration\n\n| Relationship | Opening | Closing |\n|---|---|---|\n| Close colleague | Hi [first name], | Thanks \u002F Cheers |\n| Professional peer | Hi [first name], | Best \u002F Thanks |\n| Client \u002F external | Dear [Mr.\u002FMs. Last] \u002F Hi [First], | Best regards \u002F Thank you |\n| Executive \u002F senior | Hi [First], | Thanks \u002F Best |\n| Unknown \u002F cold | Dear [First Last], | Best regards |\n\nMatch the energy the recipient uses in prior threads. When in doubt,\none step more formal than you think you need.\n\n### Draft output format\n\nProduce the email as copy-paste ready text:\n\n```\nSubject: [Subject line]\n\n[Salutation],\n\n[Body — 1-4 paragraphs, or bullets where appropriate]\n\n[Call to action or closing line]\n\n[Sign-off],\n[Name]\n[Title if applicable]\n```\n\nDo not wrap in code blocks or markdown unless the user explicitly\nwants it formatted that way.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Writing a long email when the intent can be stated in two sentences.** Longer emails get less attention, not more. Before finalizing, ask: \"what is the single thing this email must accomplish?\" Then cut everything that doesn't serve that goal. If the email needs more than one screen, it probably needs to be a document with a covering email instead.\n- **Burying the ask at the bottom.** Readers scan emails from the top. The request, decision, or key fact must appear in the first or second sentence — not after two paragraphs of background. Move context after the ask, not before.\n- **Drafting without knowing the audience's relationship and context.** An email to a close colleague who knows the project needs no preamble; the same email to an external stakeholder needs a one-sentence orientation. Always check the recipient type before setting the tone and level of detail.\n- **Using passive voice to soften bad news.** \"Mistakes were made\" and \"the deadline was missed\" avoid accountability. Professional emails about problems use active voice and first-person ownership: \"We missed the deadline\" and \"I should have flagged this earlier.\" Passive voice reads as evasive.\n- **Copying too many people.** Every extra recipient in CC adds noise and diffuses accountability. CC only people who need the information to do their job. Use BCC only for large announcements where reply-all chaos would be a problem.\n- **Treating the subject line as an afterthought.** Subjects determine whether the email is opened and found later. A vague subject (\"Question\", \"Hi\", \"Follow-up\") fails both jobs. Write the subject last, after the body is clear, so it accurately reflects the content.\n- **Sending the first draft without a read-through.** The most common email errors — wrong name, forgotten attachment, accidentally harsh phrasing, missing call to action — are caught in a single read-aloud pass. Always read the draft once from the recipient's perspective before finalizing.\n\n## Full reference\n\n### Reply vs. new thread\n\nReply to existing threads when the email is clearly part of an\nongoing conversation. Start a new thread when:\n- The topic has substantially shifted from the original subject\n- The original thread is long (>10 messages) and the new ask is\n  distinct\n- The recipient group is different from the original\n\nWhen replying, trim the quoted thread to the last 1-2 relevant\nmessages — full thread quoting adds length without value.\n\n### Sensitive topics\n\nApologies, performance feedback, salary discussions, and conflict\nresolution almost always land better in person or on video.\nIf the email must be written:\n- Lead with empathy, not defensiveness\n- Use \"I\" statements, not \"you\" statements\n- Propose a call to continue the conversation\n- Never send an angry email immediately — draft it, save it, review\n  after an hour\n\n### Templates for common scenarios\n\n**Meeting request:**\n> Subject: [Topic] — 30-min meeting request  \n> Hi [Name],  \n> I'd like to connect about [topic] — [1 sentence on why it matters\n> now]. Would you have 30 minutes available [proposed window]? Happy\n> to adjust if that doesn't work.  \n> Best, [Name]\n\n**Resignation:**\n> Subject: Resignation — [Name], effective [Date]  \n> Dear [Manager],  \n> I am writing to formally resign from my position as [title],\n> effective [date].  \n> [1-2 sentences of appreciation.]  \n> I am happy to assist with the transition in any way that would\n> be helpful.  \n> Thank you for [specific thing].  \n> Best regards, [Name]\n\n**Reference request:**\n> Subject: Reference request — [Your name], [Role] at [Company]  \n> Hi [Name],  \n> I'm applying for [role] at [company] and would be grateful if\n> you'd be willing to serve as a reference. The role is [1 line].  \n> Would you be comfortable speaking to my work on [specific\n> project\u002Fskill]? If so, they may contact you at [recruiter email]\n> in the coming [timeframe].  \n> Please let me know if you have any questions or if you'd prefer\n> not to — either is completely fine.  \n> Many thanks, [Name]\n",{"name":5,"metadata":49,"description":56},{"processkit":50},{"id":51,"layer":52,"created":53,"version":54,"category":27,"apiVersion":55},"SKILL-email-drafter",2,1775606400000,"1.0.0","processkit.projectious.work\u002Fv1","Drafts clear, professional emails ready to copy and paste — from a brief description of the situation, audience, and intent. Use when asked to write, draft, or compose an email, reply to a message, or suggest how to phrase something professionally.\n","main","4876a92620ee792aac2ac9a1a806322d8a572367","archive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.10.0\u002Fcontext\u002Fskills\u002Fproduct\u002Femail-drafter","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add projectious-work\u002Fprocesskit --skill email-drafter",{"tool":70,"command":71},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill email-drafter",{"tool":73,"command":74},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill email-drafter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.10.0\u002Fcontext\u002Fskills\u002Fproduct\u002Femail-drafter\u002FSKILL.md",true,[],[79,86,93,99,123,143],{"skillNo":80,"name":81,"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":82,"categories":83,"keywords":84,"publishedAt":85},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":85},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"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":96,"categories":97,"keywords":98,"publishedAt":85},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"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":108,"publishedAt":44},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[105],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[109,110,111,28,112,113,41,114,115,116,117,118,101,119,120,121,122],"management","skill management","ontology","create","as","transition","get","manage","update","alpha","list","package","skill package","manifests",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":44},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[129],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[131,132,109,133,134,135,136,137,138,139,140,141,41,115,116,118,142],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":44},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[150,109,151,152,112,153,154,155,41,115,156,157,117,158,118,159,160,161,162,163],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","query","facts","log"]