[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71PA7ENJKDYH7SE4P7E2BYV":3,"skill-same:01M71PA7ENJKDYH7SE4P7E2BYV":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M71PA7ENJKDYH7SE4P7E2BYV","weekly-prep-brief",null,"Generate a comprehensive weekly briefing for all external calls in the next 7 days. Triggers on 'weekly prep brief', 'prepare my week', 'what calls do I have this week', 'Monday prep', or any weekly planning request.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fweekly-prep-brief\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fweekly-prep-brief\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"weekly","weekly prep brief","prep","brief","triggers","calls","for","planning","do","my","request","generate","next","work","common","knowledge","briefing","weekly planning","what calls","monday","2026-11-10 13:02:02",false,"---\nname: weekly-prep-brief\ndescription: \"Generate a comprehensive weekly briefing for all external calls in the next 7 days. Triggers on 'weekly prep brief', 'prepare my week', 'what calls do I have this week', 'Monday prep', or any weekly planning request.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"partner-built\u002Fcommon-room\u002Fskills\u002Fweekly-prep-brief\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\n---\n# Weekly Prep Brief\n\nGenerate a single comprehensive weekly briefing that covers every external customer or prospect call in the next 7 days, with per-meeting account and contact research from Common Room.\n\n## Briefing Process\n\n### Step 1: Get the Week's External Meetings\n\n**Option A — Calendar connected:**\nUse the `~~calendar` connector to fetch all meetings scheduled in the next 7 days (or a user-specified range). Filter to keep only external meetings — those with attendees from outside your organization. Discard internal-only meetings, one-on-ones with colleagues, and recurring internal syncs.\n\nIdentify for each external meeting:\n- Company name\n- Meeting date and time\n- External attendee names and email addresses\n\n**Option B — No calendar connected:**\nAsk the user: \"To build your weekly prep brief, I'll need your upcoming external calls. Please list them: company name, date\u002Ftime, and attendee names.\"\n\nAccept freeform input and parse it into a structured list before proceeding.\n\n### Step 2: Confirm the Meeting List\n\nPresent the identified meetings to the user for confirmation before beginning research:\n\n> \"Here are the external calls I found for this week. Let me know if anything's missing or should be excluded:\n> - [Company] — [Day], [Time] — [Attendees]\n> - ...\"\n\nThis prevents wasted research on cancelled or incorrect meetings.\n\n### Step 3: Research Each Meeting\n\nFor each confirmed external meeting, run in parallel where possible:\n1. **Account research** — full account snapshot using the account-research skill\n2. **Contact research** — profile for each external attendee using the contact-research skill\n\nCommon Room data is the primary source. After CR research, run a quick **recency check** for each company — this is supplementary, not primary:\n- Search `\"[company name]\" news` scoped to the last 7 days\n- For executive attendees, search their name for recent public posts or interviews\n- Only include findings that are genuinely noteworthy (funding, leadership changes, major press). Don't pad the brief with generic news.\n\nDepth calibration:\n- For high-priority accounts (large accounts, open opportunities, renewal risk), produce full depth research\n- For lower-priority or short meetings, produce abbreviated snapshots (3–4 bullets each)\n\n### Step 4: Synthesize the Weekly Brief\n\nCompile all per-meeting research into a single structured document, sorted by meeting date\u002Ftime.\n\nOpen with a brief week-level overview that flags:\n- Any accounts with urgent signals (at-risk, trial expiring, expansion opportunity)\n- Any meetings that need special preparation or executive involvement\n- Total external call count and estimated time commitment\n\n## Output Format\n\n```\n# Weekly Prep Brief — Week of [Date]\n\n## Week Overview\n[2–4 bullets: key themes, flagged priorities, call count]\n\n---\n\n## [Monday \u002F Tuesday \u002F etc.]\n\n### [Company Name] — [Time]\n**Attendees:** [Names and titles]\n**Meeting type:** [Discovery \u002F QBR \u002F Renewal \u002F Expansion \u002F etc. — inferred if possible]\n\n**Company Snapshot**\n[4–5 bullets: account status, top signals, recent activity]\n\n**Attendee Profiles**\n- **[Name]** ([Title]): [2–3 bullets on their signals, persona, conversation angle]\n- [Repeat per attendee]\n\n**Top Signals This Week**\n[2–3 most relevant signals for this specific call]\n\n**This Week's News** [If notable news found]\n[Only genuinely noteworthy findings — funding, leadership changes, major press]\n\n**Recommended Objectives**\n[1–2 sentences: what to accomplish in this meeting]\n\n---\n\n[Repeat per meeting, sorted by date\u002Ftime]\n```\n\n## When a Meeting Has Sparse Data\n\nIf Common Room returns limited data for a particular meeting's account or attendees, use a compressed format for that meeting instead of the full template:\n\n```\n### [Company Name] — [Time] ⚠️ Limited Data\n**Attendees:** [Names and titles if known]\n**Data available:** [What Common Room actually returned]\n\n**Web Search Results**\n[Findings from web search — company news, attendee LinkedIn profiles]\n\n**Note:** Common Room has limited data on this account. The rep may want to check directly in CR or gather context from colleagues before this call.\n```\n\nDo not generate a full meeting prep section (company snapshot, signal highlights, talking points, recommended objectives) from sparse data. A short honest section is more useful than a fabricated full one.\n\n## Quality Standards\n\n- Keep each meeting section scannable — reps read these in the morning, often on mobile\n- Always sort by date\u002Ftime ascending\n- Flag urgent situations prominently (risk, trial expiration, open opps) — don't bury them\n- If a meeting has very thin Common Room data, use the sparse-data format above — never fill the full template with guesses\n- Total brief should be readable in 10–15 minutes for a week with 4–6 meetings\n- **Every fact must come from a tool call** — no invented deal context, activity, or signals\n\n## Reference Files\n\n- **`references\u002Fbriefing-guide.md`** — guidelines for structuring briefings, prioritization logic, and how to handle edge cases (cancelled meetings, new accounts with no data, etc.)\n","# Weekly Prep Brief\n\nGenerate a single comprehensive weekly briefing that covers every external customer or prospect call in the next 7 days, with per-meeting account and contact research from Common Room.\n\n## Briefing Process\n\n### Step 1: Get the Week's External Meetings\n\n**Option A — Calendar connected:**\nUse the `~~calendar` connector to fetch all meetings scheduled in the next 7 days (or a user-specified range). Filter to keep only external meetings — those with attendees from outside your organization. Discard internal-only meetings, one-on-ones with colleagues, and recurring internal syncs.\n\nIdentify for each external meeting:\n- Company name\n- Meeting date and time\n- External attendee names and email addresses\n\n**Option B — No calendar connected:**\nAsk the user: \"To build your weekly prep brief, I'll need your upcoming external calls. Please list them: company name, date\u002Ftime, and attendee names.\"\n\nAccept freeform input and parse it into a structured list before proceeding.\n\n### Step 2: Confirm the Meeting List\n\nPresent the identified meetings to the user for confirmation before beginning research:\n\n> \"Here are the external calls I found for this week. Let me know if anything's missing or should be excluded:\n> - [Company] — [Day], [Time] — [Attendees]\n> - ...\"\n\nThis prevents wasted research on cancelled or incorrect meetings.\n\n### Step 3: Research Each Meeting\n\nFor each confirmed external meeting, run in parallel where possible:\n1. **Account research** — full account snapshot using the account-research skill\n2. **Contact research** — profile for each external attendee using the contact-research skill\n\nCommon Room data is the primary source. After CR research, run a quick **recency check** for each company — this is supplementary, not primary:\n- Search `\"[company name]\" news` scoped to the last 7 days\n- For executive attendees, search their name for recent public posts or interviews\n- Only include findings that are genuinely noteworthy (funding, leadership changes, major press). Don't pad the brief with generic news.\n\nDepth calibration:\n- For high-priority accounts (large accounts, open opportunities, renewal risk), produce full depth research\n- For lower-priority or short meetings, produce abbreviated snapshots (3–4 bullets each)\n\n### Step 4: Synthesize the Weekly Brief\n\nCompile all per-meeting research into a single structured document, sorted by meeting date\u002Ftime.\n\nOpen with a brief week-level overview that flags:\n- Any accounts with urgent signals (at-risk, trial expiring, expansion opportunity)\n- Any meetings that need special preparation or executive involvement\n- Total external call count and estimated time commitment\n\n## Output Format\n\n```\n# Weekly Prep Brief — Week of [Date]\n\n## Week Overview\n[2–4 bullets: key themes, flagged priorities, call count]\n\n---\n\n## [Monday \u002F Tuesday \u002F etc.]\n\n### [Company Name] — [Time]\n**Attendees:** [Names and titles]\n**Meeting type:** [Discovery \u002F QBR \u002F Renewal \u002F Expansion \u002F etc. — inferred if possible]\n\n**Company Snapshot**\n[4–5 bullets: account status, top signals, recent activity]\n\n**Attendee Profiles**\n- **[Name]** ([Title]): [2–3 bullets on their signals, persona, conversation angle]\n- [Repeat per attendee]\n\n**Top Signals This Week**\n[2–3 most relevant signals for this specific call]\n\n**This Week's News** [If notable news found]\n[Only genuinely noteworthy findings — funding, leadership changes, major press]\n\n**Recommended Objectives**\n[1–2 sentences: what to accomplish in this meeting]\n\n---\n\n[Repeat per meeting, sorted by date\u002Ftime]\n```\n\n## When a Meeting Has Sparse Data\n\nIf Common Room returns limited data for a particular meeting's account or attendees, use a compressed format for that meeting instead of the full template:\n\n```\n### [Company Name] — [Time] ⚠️ Limited Data\n**Attendees:** [Names and titles if known]\n**Data available:** [What Common Room actually returned]\n\n**Web Search Results**\n[Findings from web search — company news, attendee LinkedIn profiles]\n\n**Note:** Common Room has limited data on this account. The rep may want to check directly in CR or gather context from colleagues before this call.\n```\n\nDo not generate a full meeting prep section (company snapshot, signal highlights, talking points, recommended objectives) from sparse data. A short honest section is more useful than a fabricated full one.\n\n## Quality Standards\n\n- Keep each meeting section scannable — reps read these in the morning, often on mobile\n- Always sort by date\u002Ftime ascending\n- Flag urgent situations prominently (risk, trial expiration, open opps) — don't bury them\n- If a meeting has very thin Common Room data, use the sparse-data format above — never fill the full template with guesses\n- Total brief should be readable in 10–15 minutes for a week with 4–6 meetings\n- **Every fact must come from a tool call** — no invented deal context, activity, or signals\n\n## Reference Files\n\n- **`references\u002Fbriefing-guide.md`** — guidelines for structuring briefings, prioritization logic, and how to handle edge cases (cancelled meetings, new accounts with no data, etc.)\n",{"name":5,"tags":49,"tools":50,"source":51,"license":14,"description":7,"source_path":52,"source_commit":53},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","partner-built\u002Fcommon-room\u002Fskills\u002Fweekly-prep-brief","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fweekly-prep-brief",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add monoes\u002Fmonomind --skill weekly-prep-brief",{"tool":69,"command":70},"bunx","bunx skills add monoes\u002Fmonomind --skill weekly-prep-brief",{"tool":72,"command":73},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill weekly-prep-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fweekly-prep-brief\u002FSKILL.md",true,[77,82],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fbriefing-guide.md","REFERENCE","参考文档",1889,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fweekly-prep-brief\u002Freferences\u002Fbriefing-guide.md",[89,115,150,175,199,225],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":44},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[96,97,98,99,100,101,102,39,103,104,105,106,107,108,109,110,111,112,113,114],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":119,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":131,"publishedAt":44},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[123,126],{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[132,133,134,100,135,136,137,138,104,139,140,141,142,143,144,145,146,147,148,149],"writing","writing plans","plans","superpowers","implementation plan","when","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":154,"sourceHtmlUrl":155,"categories":156,"keywords":160,"publishedAt":44},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[157],{"categoryNo":158,"categoryName":159,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000031","产品经理",[143,161,162,163,164,39,165,137,166,167,37,142,34,168,169,170,171,172,173,174],"write spec","spec","user request","problem","acceptance","ask","vague","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":179,"sourceHtmlUrl":180,"categories":181,"keywords":185,"publishedAt":44},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[182],{"categoryNo":183,"categoryName":184,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000033","数据分析师",[104,143,186,187,30,188,39,173,137,189,190,191,192,37,193,194,195,196,197,198],"write query","postgres","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":211,"publishedAt":44},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[205,208],{"categoryNo":206,"categoryName":207,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[212,213,214,215,30,216,217,28,218,103,219,220,221,104,107,193,222,223,224,195],"Workflow Automation","automation","workflow","parallel","actions","ci","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":232,"publishedAt":44},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[231],{"categoryNo":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},[214,233,234,235,236,237,31,30,238,239,139,240,241,242,107,193,243,244,195,245],"workflow architect","architect","trees","user journeys","branch","map","workflows","architecture","state","leadership","recovery","operations","systems"]