[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CTFN6XKZBB9TTVW5ZP5CWC":3,"skill-same:01M6CTFN6XKZBB9TTVW5ZP5CWC":76},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":65},"01M6CTFN6XKZBB9TTVW5ZP5CWC","security-posture",null,"Summarizes open threats, scan status, compliance gaps and manual checkpoints into one security snapshot. Use to review security health or before a major release.","vibbs\u002Fcompany-os","vibbs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7379149?v=4","01M6CT6M03CAS1H7RA89F3965B","Vibbs Dod","01M6CT6M4MY60C9FFQ3AAR2RSK",6,"MIT","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fsecurity-posture\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35],"security","security posture","review","status","release","compliance","health","open","snapshot","use","delta","scan","2026-11-10 10:12:30",false,"---\nname: security-posture\ndescription: Summarizes open threats, scan status, compliance gaps and manual checkpoints into one security snapshot. Use to review security health or before a major release.\nruntimes:\n  claude:\n    user-invocable: true\n    argument-hint: \"[--full | --quick | --delta]\"\n---\n\n# Security Posture\n\n## Reference\n- **ID**: S-RISK-04\n- **Category**: Ops & Risk\n- **Inputs**: artifacts\u002Fsecurity-reviews\u002F, standards\u002Fsecurity\u002Fsecurity-posture.md, company.config.yaml\n- **Outputs**: posture snapshot artifact → artifacts\u002Fsecurity-reviews\u002FPOSTURE-{date}.md\n- **Used by**: Ops & Risk Agent\n- **Tool scripts**: .\u002Ftools\u002Fsecurity\u002Fposture-check.sh, .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\n\nProduces a cross-cutting security posture snapshot that aggregates findings from all threat models, scans, and compliance checks into a single artifact. Unlike threat-modeling (which analyzes one feature), security-posture evaluates the project's overall security health.\n\n## When to Use\n\n- Before any release — posture snapshot is part of release readiness (Bar 3)\n- After resolving a security incident — verify the fix improved posture\n- Monthly, if the project is in `growth` or `scale` stage\n- When the user asks \"how's our security?\" or \"are we ready to ship?\"\n\n## Modes\n\n| Mode | What It Does |\n|------|-------------|\n| `--full` (default) | Complete posture assessment: findings, scans, compliance, checkpoints |\n| `--quick` | Summary only: open finding count, scan freshness, overall verdict |\n| `--delta` | Changes since last POSTURE- artifact: new findings, resolved findings, status changes |\n\n## Procedure\n\n### Step 1: Load Standard\n\nRead `standards\u002Fsecurity\u002Fsecurity-posture.md` for:\n- Tool tiering definitions (Tier 0-3)\n- Secrets policy requirements\n- Mandatory human-review checkpoint definitions\n- Safe execution defaults\n\nIf the standard does not exist, warn the user: \"Security posture standard not found at standards\u002Fsecurity\u002Fsecurity-posture.md. Create it first or run \u002Fship to generate the full governance layer.\"\n\n### Step 2: Load Configuration\n\nRead `company.config.yaml` for:\n- `company.stage` — determines enforcement level\n- `ai.llm_provider` — triggers AI safety checks if set\n- `architecture.*` — context for infrastructure security\n- `observability.*` — context for logging\u002Fmonitoring coverage\n\n### Step 3: Scan Threat Models\n\nFind all artifacts in `artifacts\u002Fsecurity-reviews\u002F` (exclude POSTURE- artifacts):\n- Extract YAML frontmatter: `id`, `status`, `created`\n- Scan body for severity markers: `CRITICAL`, `HIGH`, `MEDIUM`, `LOW`\n- For each finding, extract: description, severity, status (open\u002Fmitigated\u002Faccepted), age (days since created)\n\nCategorize:\n- **Open CRITICAL**: must be resolved before release\n- **Open HIGH**: should be resolved; acceptable with documented mitigation\n- **Open MEDIUM**: tracked, resolution timeline recommended\n- **Open LOW**: noted, no action required\n\n### Step 4: Check Scan Freshness\n\nLook for evidence of recent security scans:\n- Check if `dependency-scan.sh` has been run (look for output in conversation or scan result artifacts)\n- Check if `secrets-scan.sh` has been run\n- Check if `sast.sh` has been run\n\nReport last-known scan date and result for each. If no evidence of a scan: \"UNKNOWN — run `.\u002Ftools\u002Fsecurity\u002F{tool}.sh` to establish baseline.\"\n\n### Step 5: Compliance Gap Check\n\nFor each section of the security posture standard, assess compliance:\n\n| Section | Check |\n|---------|-------|\n| Tool Tiering | Are all tools classified? Are tier boundaries respected in recent agent actions? |\n| Secrets Policy | Does `.env.example` exist? Is `.env` in `.gitignore`? Has `secrets-scan.sh` been run? |\n| Human Checkpoints | Have any Tier 3 operations occurred without documented confirmation? |\n| Safe Execution Defaults | Are artifacts validated before promotion? Are dry-runs used? |\n\nRate each: `COMPLIANT` \u002F `PARTIAL` \u002F `GAP` \u002F `NOT ASSESSED`\n\n### Step 6: Human Checkpoint Audit (--full mode only)\n\nReview recent artifacts for Tier 3 operations:\n- Check `artifacts\u002Fdecision-memos\u002F` for INC- (incident) records involving production changes\n- Check recent commits for production-impacting changes\n- Flag any Tier 3 operations that lack a documented confirmation record\n\n### Step 7: Produce Posture Snapshot\n\nGenerate `artifacts\u002Fsecurity-reviews\u002FPOSTURE-{date}.md`:\n\n```yaml\n---\nid: POSTURE-{date}\ntype: security-review\ntitle: \"Security Posture Snapshot — {date}\"\nstatus: draft\ncreated: {date}\n---\n```\n\nBody structure:\n\n```markdown\n## Executive Summary\n\n**Overall Verdict**: [HEALTHY | CAUTION | AT RISK]\n\n- Open CRITICAL findings: X\n- Open HIGH findings: X\n- Scan coverage: X\u002F3 tools run in last 30 days\n- Compliance gaps: X sections with gaps\n\n## Open Findings\n\n| # | Finding | Severity | Source Artifact | Age (days) | Status |\n|---|---------|----------|----------------|------------|--------|\n| 1 | ... | CRITICAL | SEC-001 | 14 | Open |\n\n## Scan Coverage\n\n| Tool | Last Run | Result | Freshness |\n|------|----------|--------|-----------|\n| dependency-scan.sh | {date} | PASS\u002FFAIL | Fresh\u002FStale\u002FUnknown |\n| secrets-scan.sh | {date} | PASS\u002FFAIL | Fresh\u002FStale\u002FUnknown |\n| sast.sh | {date} | PASS\u002FFAIL | Fresh\u002FStale\u002FUnknown |\n\n## Compliance Status\n\n| Standard Section | Status | Notes |\n|-----------------|--------|-------|\n| Tool Tiering Policy | COMPLIANT\u002FGAP | |\n| Secrets Policy | COMPLIANT\u002FGAP | |\n| Human Checkpoints | COMPLIANT\u002FGAP | |\n| Safe Execution Defaults | COMPLIANT\u002FGAP | |\n\n## Recommendations\n\n1. [Highest priority action]\n2. [Second priority action]\n...\n```\n\n### Step 8: Run CLI Check\n\nExecute `.\u002Ftools\u002Fsecurity\u002Fposture-check.sh` and incorporate its output into the snapshot. If the tool exits non-zero, flag the specific failures in the Recommendations section.\n\n### Step 9: Validate\n\nRun `.\u002Ftools\u002Fartifact\u002Fvalidate.sh` on the saved artifact.\n\n### Step 10: Report to User\n\nPresent the Executive Summary and Recommendations. If `--quick` mode, present only the summary line and finding counts. If `--delta` mode, present a diff against the previous POSTURE- artifact.\n\n## Quality Checklist\n- [ ] Security posture standard was loaded and referenced\n- [ ] All security-review artifacts were scanned (not just the most recent)\n- [ ] Scan freshness is accurately reported (not assumed)\n- [ ] Compliance gaps are specific, not generic\n- [ ] Recommendations are actionable and prioritized\n- [ ] Artifact passes validation\n- [ ] posture-check.sh was run and its output incorporated\n\n## Cross-References\n- **threat-modeling** (S-RISK-01) — produces per-feature threat models that this skill aggregates\n- **release-readiness-gate** — posture snapshot is checked at Bar 3 (Security & Risk)\n- **security-posture standard** — `standards\u002Fsecurity\u002Fsecurity-posture.md`\n- **posture-check.sh** — `.\u002Ftools\u002Fsecurity\u002Fposture-check.sh` (CLI companion)\n","# Security Posture\n\n## Reference\n- **ID**: S-RISK-04\n- **Category**: Ops & Risk\n- **Inputs**: artifacts\u002Fsecurity-reviews\u002F, standards\u002Fsecurity\u002Fsecurity-posture.md, company.config.yaml\n- **Outputs**: posture snapshot artifact → artifacts\u002Fsecurity-reviews\u002FPOSTURE-{date}.md\n- **Used by**: Ops & Risk Agent\n- **Tool scripts**: .\u002Ftools\u002Fsecurity\u002Fposture-check.sh, .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\n\nProduces a cross-cutting security posture snapshot that aggregates findings from all threat models, scans, and compliance checks into a single artifact. Unlike threat-modeling (which analyzes one feature), security-posture evaluates the project's overall security health.\n\n## When to Use\n\n- Before any release — posture snapshot is part of release readiness (Bar 3)\n- After resolving a security incident — verify the fix improved posture\n- Monthly, if the project is in `growth` or `scale` stage\n- When the user asks \"how's our security?\" or \"are we ready to ship?\"\n\n## Modes\n\n| Mode | What It Does |\n|------|-------------|\n| `--full` (default) | Complete posture assessment: findings, scans, compliance, checkpoints |\n| `--quick` | Summary only: open finding count, scan freshness, overall verdict |\n| `--delta` | Changes since last POSTURE- artifact: new findings, resolved findings, status changes |\n\n## Procedure\n\n### Step 1: Load Standard\n\nRead `standards\u002Fsecurity\u002Fsecurity-posture.md` for:\n- Tool tiering definitions (Tier 0-3)\n- Secrets policy requirements\n- Mandatory human-review checkpoint definitions\n- Safe execution defaults\n\nIf the standard does not exist, warn the user: \"Security posture standard not found at standards\u002Fsecurity\u002Fsecurity-posture.md. Create it first or run \u002Fship to generate the full governance layer.\"\n\n### Step 2: Load Configuration\n\nRead `company.config.yaml` for:\n- `company.stage` — determines enforcement level\n- `ai.llm_provider` — triggers AI safety checks if set\n- `architecture.*` — context for infrastructure security\n- `observability.*` — context for logging\u002Fmonitoring coverage\n\n### Step 3: Scan Threat Models\n\nFind all artifacts in `artifacts\u002Fsecurity-reviews\u002F` (exclude POSTURE- artifacts):\n- Extract YAML frontmatter: `id`, `status`, `created`\n- Scan body for severity markers: `CRITICAL`, `HIGH`, `MEDIUM`, `LOW`\n- For each finding, extract: description, severity, status (open\u002Fmitigated\u002Faccepted), age (days since created)\n\nCategorize:\n- **Open CRITICAL**: must be resolved before release\n- **Open HIGH**: should be resolved; acceptable with documented mitigation\n- **Open MEDIUM**: tracked, resolution timeline recommended\n- **Open LOW**: noted, no action required\n\n### Step 4: Check Scan Freshness\n\nLook for evidence of recent security scans:\n- Check if `dependency-scan.sh` has been run (look for output in conversation or scan result artifacts)\n- Check if `secrets-scan.sh` has been run\n- Check if `sast.sh` has been run\n\nReport last-known scan date and result for each. If no evidence of a scan: \"UNKNOWN — run `.\u002Ftools\u002Fsecurity\u002F{tool}.sh` to establish baseline.\"\n\n### Step 5: Compliance Gap Check\n\nFor each section of the security posture standard, assess compliance:\n\n| Section | Check |\n|---------|-------|\n| Tool Tiering | Are all tools classified? Are tier boundaries respected in recent agent actions? |\n| Secrets Policy | Does `.env.example` exist? Is `.env` in `.gitignore`? Has `secrets-scan.sh` been run? |\n| Human Checkpoints | Have any Tier 3 operations occurred without documented confirmation? |\n| Safe Execution Defaults | Are artifacts validated before promotion? Are dry-runs used? |\n\nRate each: `COMPLIANT` \u002F `PARTIAL` \u002F `GAP` \u002F `NOT ASSESSED`\n\n### Step 6: Human Checkpoint Audit (--full mode only)\n\nReview recent artifacts for Tier 3 operations:\n- Check `artifacts\u002Fdecision-memos\u002F` for INC- (incident) records involving production changes\n- Check recent commits for production-impacting changes\n- Flag any Tier 3 operations that lack a documented confirmation record\n\n### Step 7: Produce Posture Snapshot\n\nGenerate `artifacts\u002Fsecurity-reviews\u002FPOSTURE-{date}.md`:\n\n```yaml\n---\nid: POSTURE-{date}\ntype: security-review\ntitle: \"Security Posture Snapshot — {date}\"\nstatus: draft\ncreated: {date}\n---\n```\n\nBody structure:\n\n```markdown\n## Executive Summary\n\n**Overall Verdict**: [HEALTHY | CAUTION | AT RISK]\n\n- Open CRITICAL findings: X\n- Open HIGH findings: X\n- Scan coverage: X\u002F3 tools run in last 30 days\n- Compliance gaps: X sections with gaps\n\n## Open Findings\n\n| # | Finding | Severity | Source Artifact | Age (days) | Status |\n|---|---------|----------|----------------|------------|--------|\n| 1 | ... | CRITICAL | SEC-001 | 14 | Open |\n\n## Scan Coverage\n\n| Tool | Last Run | Result | Freshness |\n|------|----------|--------|-----------|\n| dependency-scan.sh | {date} | PASS\u002FFAIL | Fresh\u002FStale\u002FUnknown |\n| secrets-scan.sh | {date} | PASS\u002FFAIL | Fresh\u002FStale\u002FUnknown |\n| sast.sh | {date} | PASS\u002FFAIL | Fresh\u002FStale\u002FUnknown |\n\n## Compliance Status\n\n| Standard Section | Status | Notes |\n|-----------------|--------|-------|\n| Tool Tiering Policy | COMPLIANT\u002FGAP | |\n| Secrets Policy | COMPLIANT\u002FGAP | |\n| Human Checkpoints | COMPLIANT\u002FGAP | |\n| Safe Execution Defaults | COMPLIANT\u002FGAP | |\n\n## Recommendations\n\n1. [Highest priority action]\n2. [Second priority action]\n...\n```\n\n### Step 8: Run CLI Check\n\nExecute `.\u002Ftools\u002Fsecurity\u002Fposture-check.sh` and incorporate its output into the snapshot. If the tool exits non-zero, flag the specific failures in the Recommendations section.\n\n### Step 9: Validate\n\nRun `.\u002Ftools\u002Fartifact\u002Fvalidate.sh` on the saved artifact.\n\n### Step 10: Report to User\n\nPresent the Executive Summary and Recommendations. If `--quick` mode, present only the summary line and finding counts. If `--delta` mode, present a diff against the previous POSTURE- artifact.\n\n## Quality Checklist\n- [ ] Security posture standard was loaded and referenced\n- [ ] All security-review artifacts were scanned (not just the most recent)\n- [ ] Scan freshness is accurately reported (not assumed)\n- [ ] Compliance gaps are specific, not generic\n- [ ] Recommendations are actionable and prioritized\n- [ ] Artifact passes validation\n- [ ] posture-check.sh was run and its output incorporated\n\n## Cross-References\n- **threat-modeling** (S-RISK-01) — produces per-feature threat models that this skill aggregates\n- **release-readiness-gate** — posture snapshot is checked at Bar 3 (Security & Risk)\n- **security-posture standard** — `standards\u002Fsecurity\u002Fsecurity-posture.md`\n- **posture-check.sh** — `.\u002Ftools\u002Fsecurity\u002Fposture-check.sh` (CLI companion)\n",{"name":5,"runtimes":41,"description":7},{"claude":42},{"argument-hint":43,"user-invocable":44},"[--full | --quick | --delta]",true,"main","e842fb6d0e04360c47db78bc2e2e2987314d64d4","os\u002Fskills\u002Fsecurity-posture",2,"https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os","https:\u002F\u002Fgithub.com\u002Fvibbs","Principal Engineer · Applied AI · building ArcAI @ GrowthArc","2026-10-21 02:08:08",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":44},[55,58,61],{"tool":56,"command":57},"npx","npx skills add vibbs\u002Fcompany-os --skill security-posture",{"tool":59,"command":60},"bunx","bunx skills add vibbs\u002Fcompany-os --skill security-posture",{"tool":62,"command":63},"pnpm","pnpm dlx skills add vibbs\u002Fcompany-os --skill security-posture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fsecurity-posture\u002FSKILL.md",[66,72],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fapi_quick_reference.md","REFERENCE","参考文档",16037,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fcobrapy\u002Freferences\u002Fapi_quick_reference.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fworkflows.md",21742,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fcobrapy\u002Freferences\u002Fworkflows.md",[77,86,94,104,120,138],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":36},"01M6CTHBW1E64ECYGD105N4S5E","typo-field","Fixture skill with a misspelled top-level field.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Ftypo-field\u002FSKILL.md",[],[84,85],"typo field","fixture skill",{"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":36},"01M6CTHABTV8FKVDHFMMKPAV51","spaced-comments","Fixture skill with comments and spaces after block keys.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fspaced-comments\u002FSKILL.md",[],[93,85],"spaced comments",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":36},"01M6CTH8MHC14KB65ZDHYBJW1N","crlf-comments","Fixture skill with Windows line endings.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fcrlf-comments\u002FSKILL.md",[],[101,102,103,85],"crlf comments","CRLF","windows",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":36},"01M6CTH6TBKTDP9G8QB1Z2K0TY","claude-fields","Fixture skill using top-level fields Claude Code documents.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fclaude-fields\u002FSKILL.md",[],[111,112,113,114,115,116,85,117,118,119],"claude fields","explore","documents","src","grep","read","Bash","code","testing",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":131,"publishedAt":36},"01M6CTH46BGKXH80RWS876Y2CW","workflow-router","Maps an objective to the artifacts, stages and agents it needs. Use when deciding what happens next or which agents to involve.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[132,133,134,135,136,33,137],"workflow","router","workflow router","next","maps","artifacts",{"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":144,"publishedAt":36},"01M6CTH27653SRVP2FMEQN3J5B","weekly-review","Summarizes your week: what shipped, AI spend, support themes, security health and next priorities. Use at the end of each week.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[145,26,146,135,33,30,147,148,24],"weekly review","priorities","save","support"]