[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ESCW2H67RW0WX8TFFJZDX9":3,"skill-same:01M7ESCW2H67RW0WX8TFFJZDX9":56},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7ESCW2H67RW0WX8TFFJZDX9","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.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-kw-weekly-prep-brief\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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.\"\n---\n\n\u003C!-- Provenance: adapted from anthropics\u002Fknowledge-work-plugins (Apache-2.0, (c) Anthropic).\nOriginal skill: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Ftree\u002Fmain\u002Fpartner-built\u002Fcommon-room\u002Fskills\u002Fweekly-prep-brief. Changes for Muse AI: Claude\u002FCowork product refs -> Muse AI; MCP -> connector; CLAUDE.md -> MUSE.md; ${CLAUDE_PLUGIN_ROOT} -> this skill's directory; \u002Fplugin:command refs -> skill refs. -->\n\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","\u003C!-- Provenance: adapted from anthropics\u002Fknowledge-work-plugins (Apache-2.0, (c) Anthropic).\nOriginal skill: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Ftree\u002Fmain\u002Fpartner-built\u002Fcommon-room\u002Fskills\u002Fweekly-prep-brief. Changes for Muse AI: Claude\u002FCowork product refs -> Muse AI; MCP -> connector; CLAUDE.md -> MUSE.md; ${CLAUDE_PLUGIN_ROOT} -> this skill's directory; \u002Fplugin:command refs -> skill refs. -->\n\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",{"name":5,"description":7},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-kw-weekly-prep-brief",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill weekly-prep-brief",{"tool":38,"command":39},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill weekly-prep-brief",{"tool":41,"command":42},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill weekly-prep-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-kw-weekly-prep-brief\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"CONNECTORS.md","REFERENCE","参考文档",1346,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-kw-weekly-prep-brief\u002FCONNECTORS.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fbriefing-guide.md",1889,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-kw-weekly-prep-brief\u002Freferences\u002Fbriefing-guide.md",[57,64,72,79,86,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"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":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"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":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]