[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AF3ABA7YCGYRAMRPFRHH42":3,"skill-same:01M7AF3ABA7YCGYRAMRPFRHH42":46},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AF3ABA7YCGYRAMRPFRHH42","weekly-review-skill",null,"Summarise open tasks, deadlines, progress, and carry-over items into a structured weekly reset. Use when starting or ending your week, reviewing what got done, or planning the week ahead. Trigger with \"weekly review\", \"what's on my plate\", \"week in review\".","innFactory-AI\u002Fcompany-ai-stack-skills","innFactory-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F165681221?v=4","01M7AEC27VD0D1QX2XBX441MDW","innFactory AI","01M7AEC28G25HQ9H9SN58MNV27",0,"MIT","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fproductivity\u002Fweekly-review-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: weekly-review-skill\ndescription: Summarise open tasks, deadlines, progress, and carry-over items into a structured weekly reset. Use when starting or ending your week, reviewing what got done, or planning the week ahead. Trigger with \"weekly review\", \"what's on my plate\", \"week in review\".\n---\n\n# Weekly Review Skill\n\nGather open work, assess progress, surface blockers, and produce a clear plan for the week ahead — all in one structured pass. Data comes from you, a connected MCP source, or companyRAG collections.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **Task manager via MCP** (e.g. Jira, Linear, Asana, Todoist, Monday.com, Notion) | Open tasks, due dates, status, assignee |\n| **Calendar via MCP** (e.g. Google Calendar, Outlook Calendar) | Upcoming meetings, time blocks, deadlines |\n| **Email & chat via MCP** (e.g. Gmail, Outlook, Slack, Microsoft Teams) | Action items from correspondence, commitments made in conversations, mentions |\n| **companyM365** (if enabled) | Outlook calendar and mail, Teams messages, Microsoft To Do and Planner tasks from your Microsoft 365 account |\n| **companyRAG \u002F file upload** | Review templates, project briefs, meeting notes with action items |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Review Workflow\n\nRun these steps in order. The review is most effective when done at a consistent time — either Friday afternoon (close the week) or Monday morning (open the week).\n\n### Step 1: Gather Open Items\n\nCollect everything that is in-flight, overdue, or upcoming:\n\n**From task managers** (if connected):\n\n- All tasks assigned to the user with status ≠ Done\u002FClosed\n- Tasks completed this week (for the retrospective)\n- Tasks due in the next 7 days\n- Tasks overdue\n\n**From calendar** (if connected):\n\n- Meetings and events for the coming week\n- Deadlines or milestones appearing as calendar events\n- Recurring commitments (standups, 1:1s, reviews)\n\n**From email and chat** (if connected):\n\n- Action items from the past week's correspondence\n- Outstanding replies or commitments\n- Mentions requiring follow-up\n\n**From user input**:\n\n- Any tasks, projects, or commitments not captured in tools\n- Personal goals or development items\n- Items remembered during the review process\n\n### Step 2: Categorise and Assess\n\nOrganise gathered items into these categories:\n\n| Category | Definition | Action |\n| --- | --- | --- |\n| **Completed this week** | Tasks finished since last review | Acknowledge and archive. Note any that took significantly longer or shorter than expected. |\n| **In progress** | Started but not finished | Assess: on track, at risk, or blocked? Estimate remaining effort. |\n| **Carry-over** | Planned for this week but not started | Why didn't it happen? Re-prioritise for next week or deliberately defer. |\n| **Overdue** | Past due date and not complete | Escalate, renegotiate deadline, or reprioritise. Overdue items need a decision, not just a note. |\n| **Upcoming (next 7 days)** | Due or scheduled for the coming week | Estimate effort and assign to specific days if possible. |\n| **Waiting on others** | Blocked by someone else's action | Note who, what, and when you last followed up. Plan a follow-up if stale. |\n| **Someday \u002F backlog** | Items with no deadline but still relevant | Review quarterly. If an item has been on this list for 4+ weeks without progress, decide: schedule it or drop it. |\n\n### Step 3: Identify Patterns and Blockers\n\nLook across the categorised items for systemic issues:\n\n- Recurring carry-over : The same task appearing as carry-over for 2+ weeks signals either over-commitment, unclear requirements, or avoidance. Name it.\n- Time allocation mismatch : If the calendar is full of meetings but the task list expects 20 hours of focused work, there is a math problem. Flag it.\n- Blocker concentration : Multiple items blocked by the same person, team, or dependency? That is a single blocker to escalate, not many separate ones.\n- Priority drift : Are urgent-but-unimportant tasks crowding out important-but-not-urgent work? Note the drift.\n\n### Step 4: Plan the Coming Week\n\nTranslate the assessment into a concrete plan:\n\n1. Select 3-5 priorities : Not a full task list — the 3-5 most important outcomes for the coming week. These are the items that, if completed, make the week a success.\n2. Time-block estimates : For each priority, estimate the focused time needed. Compare against available focused time (calendar minus meetings, minus buffer for reactive work).\n3. Day assignment (optional but recommended): Assign priorities to specific days based on deadlines, energy, and meeting patterns. Front-load the most important work.\n4. Follow-up list : Items where you need to chase someone, send an update, or check on status.\n5. Deliberate deferrals : Items explicitly pushed to a future week — not forgotten, but consciously deprioritised. Note the reason.\n\n### Step 5: Generate the Review Document\n\nProduce the structured output using the template below.\n\n## Output Template: Weekly Review\n\n```\n# Weekly Review — [Week of DATE]\n\n## Last Week: What Got Done\n  ✓ [Completed item 1]\n  ✓ [Completed item 2]\n  ✓ [Completed item 3]\n  ...\n\n  Highlights: [1-2 sentences on what went well or notable achievements]\n\n## Carried Over (Not Completed)\n  → [Item 1] — Reason: [why it didn't happen] — Decision: [do next week \u002F defer \u002F drop]\n  → [Item 2] — Reason: [...] — Decision: [...]\n\n## Currently In Progress\n  ⟳ [Item 1] — Status: [on track \u002F at risk \u002F blocked] — ETA: [estimate]\n  ⟳ [Item 2] — Status: [...] — ETA: [...]\n\n## Overdue\n  ⚠ [Item 1] — Due: [date] — Action: [renegotiate \u002F escalate \u002F complete by X]\n\n## Waiting On Others\n  ⏳ [Item 1] — Waiting on: [person] — Since: [date] — Follow-up: [plan]\n\n## This Week: Priorities\n  1. [Priority 1] — Estimated time: [hours] — Due: [date or \"no hard deadline\"]\n  2. [Priority 2] — Estimated time: [hours] — Due: [date]\n  3. [Priority 3] — Estimated time: [hours] — Due: [date]\n\n  Available focused time: ~[hours] (based on [total hours] minus [meeting hours] minus [buffer])\n\n## Follow-ups to Send\n  - [Follow-up 1] — To: [person] — By: [day]\n  - [Follow-up 2] — To: [person] — By: [day]\n\n## Deliberately Deferred\n  ↓ [Item 1] — Deferred to: [week\u002Fdate] — Reason: [why]\n\n## Patterns Noticed\n  [Any systemic observations from Step 3]\n\n## Notes for Next Review\n  [Anything to remember or check next week]\n```\n\n## Review Cadence Variants\n\nThe core methodology adapts to different cadences:\n\n| Cadence | When to Use | Modification |\n| --- | --- | --- |\n| **Weekly** (default) | Standard knowledge work | Full workflow as described above |\n| **Bi-weekly** | Lower task volume or longer project cycles | Extend the retrospective window; add a mid-cycle pulse check |\n| **Daily standup prep** | High-velocity environments | Abbreviated: skip Steps 3-4; focus on today's 1-3 items and blockers |\n| **Monthly** | Strategic\u002Fleadership review | Add: goal progress, OKR check-in, delegation assessment, team capacity |\n\n## Guardrails\n\n- NEVER fabricate task status or calendar events — if data is unavailable, ask the user.\n- NEVER prioritise for the user without their input — present items and a recommended order, framed as a suggestion.\n- NEVER estimate domain-specific work without the user's input — ask for effort estimates on technical or specialised tasks.\n- Flag outputs: `[From connected source]`, `[From user input]`, `[Suggested]`.\n\n> **Tip:** Ask for Markdown or DOCX output via companyFILES to get a formatted review ready to share.\n","# Weekly Review Skill\n\nGather open work, assess progress, surface blockers, and produce a clear plan for the week ahead — all in one structured pass. Data comes from you, a connected MCP source, or companyRAG collections.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **Task manager via MCP** (e.g. Jira, Linear, Asana, Todoist, Monday.com, Notion) | Open tasks, due dates, status, assignee |\n| **Calendar via MCP** (e.g. Google Calendar, Outlook Calendar) | Upcoming meetings, time blocks, deadlines |\n| **Email & chat via MCP** (e.g. Gmail, Outlook, Slack, Microsoft Teams) | Action items from correspondence, commitments made in conversations, mentions |\n| **companyM365** (if enabled) | Outlook calendar and mail, Teams messages, Microsoft To Do and Planner tasks from your Microsoft 365 account |\n| **companyRAG \u002F file upload** | Review templates, project briefs, meeting notes with action items |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Review Workflow\n\nRun these steps in order. The review is most effective when done at a consistent time — either Friday afternoon (close the week) or Monday morning (open the week).\n\n### Step 1: Gather Open Items\n\nCollect everything that is in-flight, overdue, or upcoming:\n\n**From task managers** (if connected):\n\n- All tasks assigned to the user with status ≠ Done\u002FClosed\n- Tasks completed this week (for the retrospective)\n- Tasks due in the next 7 days\n- Tasks overdue\n\n**From calendar** (if connected):\n\n- Meetings and events for the coming week\n- Deadlines or milestones appearing as calendar events\n- Recurring commitments (standups, 1:1s, reviews)\n\n**From email and chat** (if connected):\n\n- Action items from the past week's correspondence\n- Outstanding replies or commitments\n- Mentions requiring follow-up\n\n**From user input**:\n\n- Any tasks, projects, or commitments not captured in tools\n- Personal goals or development items\n- Items remembered during the review process\n\n### Step 2: Categorise and Assess\n\nOrganise gathered items into these categories:\n\n| Category | Definition | Action |\n| --- | --- | --- |\n| **Completed this week** | Tasks finished since last review | Acknowledge and archive. Note any that took significantly longer or shorter than expected. |\n| **In progress** | Started but not finished | Assess: on track, at risk, or blocked? Estimate remaining effort. |\n| **Carry-over** | Planned for this week but not started | Why didn't it happen? Re-prioritise for next week or deliberately defer. |\n| **Overdue** | Past due date and not complete | Escalate, renegotiate deadline, or reprioritise. Overdue items need a decision, not just a note. |\n| **Upcoming (next 7 days)** | Due or scheduled for the coming week | Estimate effort and assign to specific days if possible. |\n| **Waiting on others** | Blocked by someone else's action | Note who, what, and when you last followed up. Plan a follow-up if stale. |\n| **Someday \u002F backlog** | Items with no deadline but still relevant | Review quarterly. If an item has been on this list for 4+ weeks without progress, decide: schedule it or drop it. |\n\n### Step 3: Identify Patterns and Blockers\n\nLook across the categorised items for systemic issues:\n\n- Recurring carry-over : The same task appearing as carry-over for 2+ weeks signals either over-commitment, unclear requirements, or avoidance. Name it.\n- Time allocation mismatch : If the calendar is full of meetings but the task list expects 20 hours of focused work, there is a math problem. Flag it.\n- Blocker concentration : Multiple items blocked by the same person, team, or dependency? That is a single blocker to escalate, not many separate ones.\n- Priority drift : Are urgent-but-unimportant tasks crowding out important-but-not-urgent work? Note the drift.\n\n### Step 4: Plan the Coming Week\n\nTranslate the assessment into a concrete plan:\n\n1. Select 3-5 priorities : Not a full task list — the 3-5 most important outcomes for the coming week. These are the items that, if completed, make the week a success.\n2. Time-block estimates : For each priority, estimate the focused time needed. Compare against available focused time (calendar minus meetings, minus buffer for reactive work).\n3. Day assignment (optional but recommended): Assign priorities to specific days based on deadlines, energy, and meeting patterns. Front-load the most important work.\n4. Follow-up list : Items where you need to chase someone, send an update, or check on status.\n5. Deliberate deferrals : Items explicitly pushed to a future week — not forgotten, but consciously deprioritised. Note the reason.\n\n### Step 5: Generate the Review Document\n\nProduce the structured output using the template below.\n\n## Output Template: Weekly Review\n\n```\n# Weekly Review — [Week of DATE]\n\n## Last Week: What Got Done\n  ✓ [Completed item 1]\n  ✓ [Completed item 2]\n  ✓ [Completed item 3]\n  ...\n\n  Highlights: [1-2 sentences on what went well or notable achievements]\n\n## Carried Over (Not Completed)\n  → [Item 1] — Reason: [why it didn't happen] — Decision: [do next week \u002F defer \u002F drop]\n  → [Item 2] — Reason: [...] — Decision: [...]\n\n## Currently In Progress\n  ⟳ [Item 1] — Status: [on track \u002F at risk \u002F blocked] — ETA: [estimate]\n  ⟳ [Item 2] — Status: [...] — ETA: [...]\n\n## Overdue\n  ⚠ [Item 1] — Due: [date] — Action: [renegotiate \u002F escalate \u002F complete by X]\n\n## Waiting On Others\n  ⏳ [Item 1] — Waiting on: [person] — Since: [date] — Follow-up: [plan]\n\n## This Week: Priorities\n  1. [Priority 1] — Estimated time: [hours] — Due: [date or \"no hard deadline\"]\n  2. [Priority 2] — Estimated time: [hours] — Due: [date]\n  3. [Priority 3] — Estimated time: [hours] — Due: [date]\n\n  Available focused time: ~[hours] (based on [total hours] minus [meeting hours] minus [buffer])\n\n## Follow-ups to Send\n  - [Follow-up 1] — To: [person] — By: [day]\n  - [Follow-up 2] — To: [person] — By: [day]\n\n## Deliberately Deferred\n  ↓ [Item 1] — Deferred to: [week\u002Fdate] — Reason: [why]\n\n## Patterns Noticed\n  [Any systemic observations from Step 3]\n\n## Notes for Next Review\n  [Anything to remember or check next week]\n```\n\n## Review Cadence Variants\n\nThe core methodology adapts to different cadences:\n\n| Cadence | When to Use | Modification |\n| --- | --- | --- |\n| **Weekly** (default) | Standard knowledge work | Full workflow as described above |\n| **Bi-weekly** | Lower task volume or longer project cycles | Extend the retrospective window; add a mid-cycle pulse check |\n| **Daily standup prep** | High-velocity environments | Abbreviated: skip Steps 3-4; focus on today's 1-3 items and blockers |\n| **Monthly** | Strategic\u002Fleadership review | Add: goal progress, OKR check-in, delegation assessment, team capacity |\n\n## Guardrails\n\n- NEVER fabricate task status or calendar events — if data is unavailable, ask the user.\n- NEVER prioritise for the user without their input — present items and a recommended order, framed as a suggestion.\n- NEVER estimate domain-specific work without the user's input — ask for effort estimates on technical or specialised tasks.\n- Flag outputs: `[From connected source]`, `[From user input]`, `[Suggested]`.\n\n> **Tip:** Ask for Markdown or DOCX output via companyFILES to get a formatted review ready to share.\n",{"name":5,"description":7},"main","39e0752000720de2d20917bd46c1c5149c4a0221","en\u002Fskills\u002Fproductivity\u002Fweekly-review-skill","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills","https:\u002F\u002Fgithub.com\u002FinnFactory-AI","https:\u002F\u002Finnfactory.ai","Engineering AI. Enabling Tomorrow.","2026-11-13 19:54:47",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill weekly-review-skill",{"tool":38,"command":39},"bunx","bunx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill weekly-review-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill weekly-review-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fproductivity\u002Fweekly-review-skill\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7AF4HHK5B987T44HW7BZFVZ","sales-asset-skill","Produce tailored one-pagers, landing pages, case study drafts, and demo narratives personalised to a specific deal and buyer persona. Use when preparing collateral for a specific deal, building leave-behind materials, or customising standard assets for a prospect. Trigger with \"create a one-pager for\", \"sales deck for [deal]\", \"customise this asset for\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fsales-asset-skill\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7AF4D32V0FJE0QGCBZSQ7BW","pipeline-review-skill","Analyse deal health, surface stale or at-risk opportunities, and produce a prioritised weekly action plan. Use when preparing for a pipeline review meeting, assessing forecast accuracy, or identifying stuck deals. Trigger with \"review my pipeline\", \"pipeline health check\", \"deal risk analysis\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fpipeline-review-skill\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AF48W7G8DMAHRAM125B192","outreach-skill","Research a prospect then draft personalised outreach with research-backed hooks, subject-line variants, and follow-up sequences. Use when cold-emailing a prospect, writing LinkedIn outreach, or building a multi-touch sequence. Trigger with \"draft outreach to [person\u002Fcompany]\", \"write cold email to\", \"outreach sequence for\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Foutreach-skill\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AF43VKNPQ7G1NTQ4MRH40J","forecast-skill","Build a weighted revenue forecast with risk flags, commit recommendations, and gap-to-quota analysis. Use when preparing for a forecast call, evaluating end-of-quarter projections, or assessing pipeline coverage. Trigger with \"build forecast\", \"forecast for this quarter\", \"where do I stand against quota\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fforecast-skill\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AF3Z5N61VYSEJRYWXR4JP1","deal-strategy-skill","Map stakeholder power dynamics, surface deal risks, and recommend a step-by-step engagement strategy. Use when entering a complex deal, preparing for an executive sponsor meeting, or diagnosing a stuck opportunity. Trigger with \"plan deal strategy for\", \"stakeholder map\", \"how do I advance this deal\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fdeal-strategy-skill\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AF3VGG29AX0T2X9WQ5MWDN","call-summary-skill","Extract action items, key topics, and objections from call notes or transcripts and draft a customer-facing follow-up email. Use after a sales call, demo, or discovery session. Trigger with \"summarise this call\", \"call notes from\", \"write follow-up for this meeting\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fcall-summary-skill\u002FSKILL.md",[],[]]