[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CAEW9SW21A2DN06MN9KY6D":3,"skill-same:01M6CAEW9SW21A2DN06MN9KY6D":86},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6CAEW9SW21A2DN06MN9KY6D","weekly-review-planning",null,"Weekly reset: commitments, stalled work, next-week plan.","adnichols\u002Fai-configs","adnichols","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F493746?v=4","01M6C33VRY9WF6XWYPT1AFA7JJ","Aaron Nichols","01M6C33VWTNKGRM92E9G643V4W",5,"MIT","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fprofiles\u002Fnerd\u002Fskills\u002Fproductivity\u002Fweekly-review-planning\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"review","weekly review planning","weekly review","planning","linux","triage","windows","tasks","obsidian","inbox","email","productivity","Google-Workspace","plan","notion","workspace","work","calendar","airtable","google","2026-11-10 10:12:30",false,"---\nname: weekly-review-planning\ndescription: \"Weekly reset: commitments, stalled work, next-week plan.\"\nversion: 0.1.0\nauthor: Ben Barclay (benbarclay), Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [Weekly-Review, Planning, Tasks, Calendar, Productivity]\n    related_skills: [obsidian, notion, airtable, google-workspace, email-inbox-triage]\n---\n\n# Weekly Review and Planning\n\nRun a bounded weekly reset across the user's chosen systems. This is a concrete recurring task, not a generic productivity methodology — the `weekly-review` Automation Blueprint schedules it as a cron job.\n\n## When to Use\n\n- \"Run my weekly review.\"\n- \"What did I commit to and what is slipping?\"\n- \"Plan next week from my calendar, tasks, and notes.\"\n- \"Find stale projects and waiting items.\"\n- A cron tick fires for a scheduled weekly review.\n\nDon't use for: daily briefs (see the `google-workspace` daily-brief reference) or single-inbox triage (`email-inbox-triage`).\n\n## Procedure\n\n### 1. Set systems and window\n\nConfirm timezone, review period, planning horizon, authoritative task\u002Fproject store, calendars, inboxes, and allowed writes. Default to recommendations\u002Fdrafts, not mutations. Done when source-of-truth conflicts have a declared winner.\n\n### 2. Review calendar evidence\n\nLoad `google-workspace` or the relevant calendar connector. Inspect the completed week for meetings and commitments, then the next 1-2 weeks for deadlines, travel, preparation, and capacity. Capture follow-ups implied by past events and conflicts ahead. Done when both retrospective and horizon are covered.\n\n### 3. Clear capture inboxes\n\nReview the task inbox, notes (`obsidian`, `notion`), flagged email (`email-inbox-triage` owns thread-level triage), and other declared capture points. Convert each item to next action, project, waiting, scheduled, someday, reference, archive, or delete proposal. Do not mutate until scope is approved. Done when remaining unprocessed items are counted and stated.\n\n### 4. Reconcile active projects\n\nFor each project identify desired outcome, next action, owner, deadline, blocker, last meaningful activity, and source link. Flag projects with no next action, missed dates, duplicate records, or contradictory status. Done when every active project is actionable or explicitly paused.\n\n### 5. Review waiting and commitments\n\nFind promises made by the user and items owed by others. Propose follow-ups with dates and channels. Do not infer that silence means completion. Done when each waiting item has an owner and next review\u002Ffollow-up date.\n\n### 6. Build a capacity-aware plan\n\nEstimate fixed calendar load and select a small set of weekly outcomes plus near-term next actions. Rank by consequence, deadline, dependency, and effort; do not fill every free hour. Done when the plan fits actual capacity and names deferred work.\n\n### 7. Apply approved updates\n\nUpdate tasks\u002Fprojects, create calendar holds, archive processed items, and draft follow-ups only as approved. Read every changed record back from the provider. Done when verified writes match the review summary.\n\n## Output Shape\n\n1. Wins and completed commitments\n2. Overdue or at risk\n3. Waiting\u002Ffollow-ups\n4. Stalled or ambiguous projects\n5. Next week's outcomes and calendar constraints\n6. Proposed updates awaiting approval\n7. Coverage gaps\n\n## Pitfalls\n\n- Planning from tasks without calendar capacity.\n- Carrying every unfinished item forward as high priority.\n- Marking projects active with no next action.\n- Silently deleting or rescheduling personal commitments.\n- Treating silence from others as completion.\n\n## Verification\n\n- [ ] Both the completed week and the planning horizon were covered, or gaps are stated.\n- [ ] Every stalled\u002Fwaiting flag traces to a specific record, event, or thread.\n- [ ] No task, event, or note was mutated without approval; approved writes were read back.\n- [ ] The plan names what was deferred, not just what was chosen.\n","# Weekly Review and Planning\n\nRun a bounded weekly reset across the user's chosen systems. This is a concrete recurring task, not a generic productivity methodology — the `weekly-review` Automation Blueprint schedules it as a cron job.\n\n## When to Use\n\n- \"Run my weekly review.\"\n- \"What did I commit to and what is slipping?\"\n- \"Plan next week from my calendar, tasks, and notes.\"\n- \"Find stale projects and waiting items.\"\n- A cron tick fires for a scheduled weekly review.\n\nDon't use for: daily briefs (see the `google-workspace` daily-brief reference) or single-inbox triage (`email-inbox-triage`).\n\n## Procedure\n\n### 1. Set systems and window\n\nConfirm timezone, review period, planning horizon, authoritative task\u002Fproject store, calendars, inboxes, and allowed writes. Default to recommendations\u002Fdrafts, not mutations. Done when source-of-truth conflicts have a declared winner.\n\n### 2. Review calendar evidence\n\nLoad `google-workspace` or the relevant calendar connector. Inspect the completed week for meetings and commitments, then the next 1-2 weeks for deadlines, travel, preparation, and capacity. Capture follow-ups implied by past events and conflicts ahead. Done when both retrospective and horizon are covered.\n\n### 3. Clear capture inboxes\n\nReview the task inbox, notes (`obsidian`, `notion`), flagged email (`email-inbox-triage` owns thread-level triage), and other declared capture points. Convert each item to next action, project, waiting, scheduled, someday, reference, archive, or delete proposal. Do not mutate until scope is approved. Done when remaining unprocessed items are counted and stated.\n\n### 4. Reconcile active projects\n\nFor each project identify desired outcome, next action, owner, deadline, blocker, last meaningful activity, and source link. Flag projects with no next action, missed dates, duplicate records, or contradictory status. Done when every active project is actionable or explicitly paused.\n\n### 5. Review waiting and commitments\n\nFind promises made by the user and items owed by others. Propose follow-ups with dates and channels. Do not infer that silence means completion. Done when each waiting item has an owner and next review\u002Ffollow-up date.\n\n### 6. Build a capacity-aware plan\n\nEstimate fixed calendar load and select a small set of weekly outcomes plus near-term next actions. Rank by consequence, deadline, dependency, and effort; do not fill every free hour. Done when the plan fits actual capacity and names deferred work.\n\n### 7. Apply approved updates\n\nUpdate tasks\u002Fprojects, create calendar holds, archive processed items, and draft follow-ups only as approved. Read every changed record back from the provider. Done when verified writes match the review summary.\n\n## Output Shape\n\n1. Wins and completed commitments\n2. Overdue or at risk\n3. Waiting\u002Ffollow-ups\n4. Stalled or ambiguous projects\n5. Next week's outcomes and calendar constraints\n6. Proposed updates awaiting approval\n7. Coverage gaps\n\n## Pitfalls\n\n- Planning from tasks without calendar capacity.\n- Carrying every unfinished item forward as high priority.\n- Marking projects active with no next action.\n- Silently deleting or rescheduling personal commitments.\n- Treating silence from others as completion.\n\n## Verification\n\n- [ ] Both the completed week and the planning horizon were covered, or gaps are stated.\n- [ ] Every stalled\u002Fwaiting flag traces to a specific record, event, or thread.\n- [ ] No task, event, or note was mutated without approval; approved writes were read back.\n- [ ] The plan names what was deferred, not just what was chosen.\n",{"name":5,"author":44,"license":15,"version":45,"metadata":46,"platforms":57,"description":7},"Ben Barclay (benbarclay), Hermes Agent","0.1.0",{"hermes":47},{"tags":48,"related_skills":54},[49,50,51,52,53],"Weekly-Review","Planning","Tasks","Calendar","Productivity",[27,33,37,55,56],"google-workspace","email-inbox-triage",[23,58,25],"macos","main","64e2fc9afa7bb3da1138eb73399144d0e7e73e9d","_hermes\u002Fdefault\u002Fprofiles\u002Fnerd\u002Fskills\u002Fproductivity\u002Fweekly-review-planning",4,"https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs","https:\u002F\u002Fgithub.com\u002Fadnichols","2026-11-06 00:28:38",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add adnichols\u002Fai-configs --skill weekly-review-planning",{"tool":72,"command":73},"bunx","bunx skills add adnichols\u002Fai-configs --skill weekly-review-planning",{"tool":75,"command":76},"pnpm","pnpm dlx skills add adnichols\u002Fai-configs --skill weekly-review-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fprofiles\u002Fnerd\u002Fskills\u002Fproductivity\u002Fweekly-review-planning\u002FSKILL.md",true,[80],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fapi_reference.md","REFERENCE","参考文档",10481,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fflowio\u002Freferences\u002Fapi_reference.md",[87,106,138,163,174,190],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":39},"01M6CB7RN791P5RRRCJWWC7DAR","blocked-page-recovery","Use when a fetch fails: 403\u002F429, paywall, WAF, bot wall.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fweb\u002Fblocked-page-recovery\u002FSKILL.md",[],[94,95,96,97,98,99,100,101,102,103,104,25,105,23,58],"recovery","page","blocked page recovery","bot","fallback","use","fetch","hermes agent","hermes","Citations","waf","research",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":125,"publishedAt":39},"01M6CB7NQY2VVYCQJ1QBXACQF4","writing-plans","Use when creating or updating executable software plans. Keep plans as local files unless the user explicitly asks to register them in Doct.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[112,117,120],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":118,"categoryName":119,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[126,127,128,129,130,131,132,133,22,134,135,136,99,137,101,102,32],"writing","writing plans","documentation","test","workflow","design","user","development","files","implementation","html","ops",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":153,"publishedAt":39},"01M6CB7JME246KZQHP73Z2STDF","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[144,147,150],{"categoryNo":145,"categoryName":146,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":148,"categoryName":149,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":151,"categoryName":152,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000037","律师与法务",[129,133,154,155,156,101,102,157,32,158,159,160,58,161,23,162,25],"test driven development","red-green-refactor","superpowers","quality","refactor","code","debugging","tdd","testing",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":170,"publishedAt":39},"01M6CB7FQ407KQTD4Z9VAWKY54","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[169],{"categoryNo":148,"categoryName":149,"taxonomyType":115,"taxonomyTypeDesc":116},[160,171,133,156,101,102,172,32,173,25,129,23,58],"systematic debugging","troubleshooting","investigation",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":183,"publishedAt":39},"01M6CB7D57MK88HE5YPZHKH68Q","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[180],{"categoryNo":181,"categoryName":182,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000021","资料检索与研究",[176,25,184,185,105,186,23,58,187,188,189,101,102,32,22],"validate","experiments","prototype","feasibility","sketch","experiment",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":200,"publishedAt":39},"01M6CB7APAQ37YE5YE1MAAFT42","simplify-code","Parallel 3-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fskills\u002Fsoftware-development\u002Fsimplify-code\u002FSKILL.md",[196,197],{"categoryNo":118,"categoryName":119,"taxonomyType":115,"taxonomyTypeDesc":116},{"categoryNo":198,"categoryName":199,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000030","开发工程师",[201,202,159,203,101,102,204,32,158,205,206,207,133,25,129,23,19,58],"simplify code","simplify","subagent","parallel","code-review","delegation","cleanup"]