Agent skill · Audited from source

Weekly Checkin

skill · huytieu/COG-second-brainMIT licenceAudited 14 Oct 2026 · source 6ea1a6ff2160

★ 1,281pushed 11 days ago
✓SAFEGrade B · 89/100 · 14 Oct 2026 · 6ea1a6f
1,281repo stars · whole huytieu/COG-second-brain

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 6ea1a6ff2160 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Cross-domain pattern analysis and strategic reflection for weekly review

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Weekly Checkin (huytieu/COG-second-brain)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/huytieu/weekly-checkin

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha 6ea1a6ff2160 · 14 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publisherhuytieu GitHub userOwner of the repository this skill is read from
  • Source folderhuytieu/COG-second-brain/.claude/skills/weekly-checkinThe exact folder we audited
  • LicenceMITAs the repository states it
  • Commit pinned for this verdict6ea1a6ff2160A new audit runs when the source changes
  • Repository statusNot archivedLast push 11 days ago
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: Cross-domain pattern analysis and strategic reflection for weekly review

---
name: weekly-checkin
description: Cross-domain pattern analysis and strategic reflection for weekly review
roles: [all]
integrations: []
---

# COG Weekly Check-in Skill

## Purpose
Comprehensive weekly review and analysis integrating insights across all domains (personal, professional, projects) with pattern recognition and strategic planning.

## When to Invoke
- User wants to do their weekly review
- User says "weekly checkin", "weekly review", "reflect on my week"
- End of week reflection time
- User wants to analyze patterns across the week

## Agent Mode Awareness

**Check `agent_mode` in `00-inbox/MY-PROFILE.md` frontmatter:**
- If `agent_mode: team` — delegate domain-specific analysis to sub-agents (e.g., one for personal patterns, one for professional review, one per active project). Each agent scans relevant braindumps/briefs and returns insights. Combine into the weekly synthesis.
- If `agent_mode: solo` (default) — handle all scanning and analysis directly in the conversation. No delegation.

## Pre-Flight Check

**Check for user profile (optional but enhances experience):**

1. Look for `00-inbox/MY-PROFILE.md` in the vault
2. If found:
   - Read user's name for personalization
   - Read active projects to review project-specific progress
   - Tailor reflection questions to user's role and projects

**Get current timestamp (REQUIRED before generating any files):**

1. Run `date '+%Y-%m-%d %H:%M'` using Bash to get the actual current date and time
2. Store this value and use it for the `created:` frontmatter field
3. NEVER guess or fabricate the time — always use the value returned by the `date` command

## Process Flow

### 1. Gather Context

Scan recent files from the past week:
- Daily briefs in `01-daily/briefs/`
- Braindumps in `02-personal/braindumps/`, `03-professional/braindumps/`, `04-projects/*/braindumps/`
- Previous check-ins in `01-daily/checkins/`

If `MY-PROFILE.md` available:
- Use user's name for personalization
- Reference their active projects
- Tailor questions to their role

### 2. Guided Reflection

Lead user through reflection questions in a warm, conversational tone:

#### Overall Week Assessment
**Ask:**
- "How would you rate this week on a 1-5 scale? Why that rating?"
- "What were your biggest wins this week?"
- "What were your main challenges?"

**Listen for:**
- Overall sentiment and energy
- Key accomplishments they're proud of
- Obstacles they faced
- Emotional tone of the week

#### Domain Reviews

**Personal Domain:**
**Ask:**
- "How did you take care of yourself this week?"
- "Any personal growth or insights?"
- "How were your energy levels and well-being?"

**Professional Domain:**
**Ask:**
- "What did you accomplish at work? Any standout moments?"
- "How did things go with your team or colleagues?"
- "Any professional development or learning?"

**Projects Domain (if applicable):**
For each active project from MY-PROFILE.md:
**Ask:**
- "How did [project name] progress this week?"
- "What moved forward? What's blocking you?"
- "Any new insights or direction changes?"

#### Pattern Recognition

**Ask:**
- "Looking at your braindumps this week, did you notice any recurring themes?"
- "How did your energy levels vary throughout the week?"
- "Any connections between different areas of your life - personal, professional, projects?"
- "What surprised you this week?"

**Help identify:**
- Themes they might not see themselves
- Patterns across domains
- Evolution of thinking
- Cross-domain connections

#### Forward Planning

**Ask:**
- "What are your top 3 priorities for next week?"
- "Anything from this week you want to carry forward?"
- "What do you want to do differently next week?"
- "What success would look like next week?"

**Help with:**
- Clarifying priorities
- Being specific about goals
- Identifying experiments to try
- Setting measurable outcomes

### 3. Generate Weekly Check-in Document

Based on the conversation, create a structured check-in document:

```markdown
---
type: "weekly-checkin"
domain: "integrated"
date: "YYYY-MM-DD"
week_of: "YYYY-MM-DD"
created: "YYYY-MM-DD HH:MM"
tags: ["#weekly-checkin", "#reflection", "#planning"]
domains_analyzed: ["personal", "professional", "projects"]
rating: [1-5]
braindumps_reviewed: [count]
briefs_reviewed: [count]
---

# Weekly Check-in - Week of [Date]

## Executive Summary

**Week Rating:** [1-5] ⭐ - [User's reasoning in their words]

**In Three Words:** [word1], [word2], [word3]

**Key Highlights:**
- [Win 1 - specific and celebratory]
- [Win 2 - acknowledge effort and outcome]
- [Win 3 if applicable]

**Main Challenges:**
- [Challenge 1 - honest and clear]
- [Challenge 2 - what made it difficult]

---

## Domain Reviews

### 💭 Personal

**Wellness & Self-Care:**
[User's reflection on personal wellness, relationships, health]

**Energy Patterns:**
- [Observations about energy levels throughout the week]
- [What energized them]
- [What drained them]

**Personal Growth:**
- [Insights or realizations]
- [New habits or changes]

**Rating:** [1-5] ⭐

---

### 💼 Professional

**Accomplishments:**
[User's reflection on work accomplishments, projects completed, milestones reached]

**Team & Collaboration:**
[Insights about team dynamics, meetings, relationships]

**Challenges & Learnings:**
[What was difficult and what they learned]

**Professional Development:**
[Skills developed, knowledge gained]

**Rating:** [1-5] ⭐

---

### 🎯 Projects

[For each active project:]

#### [Project Name]

**Progress This Week:**
- [What moved forward - be specific]
- [Milestones achieved]
- [Decisions made]

**Current Status:** [On track | Needs attention | Blocked | Pivoting]

**Blockers:**
- [What's in the way - if any]
- [Dependencies waiting on]

**Insights & Direction:**
[Any strategic insights or direction changes]

**Next Steps:**
- [ ] [Specific next action 1] 📅 [YYYY-MM-DD = date of next Monday]
- [ ] [Specific next action 2] 📅 [YYYY-MM-DD = date of next Friday]
- [ ] [Specific next action 3] 📅 [YYYY-MM

Excerpt, first 6,006 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 6ea1a6f

Download folder ↗
git clone https://github.com/huytieu/COG-second-brain
git -C COG-second-brain checkout 6ea1a6ff2160

The author documents no install command, so this uses the repository directly. Our verdict covers commit 6ea1a6ff2160 only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 6ea1a6ff2160

README badge

For maintainers · shows the latest audit

ModelsAtlas: SAFE BMODELSATLASSAFE · B
[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/huytieu/weekly-checkin/badge.svg)](https://modelsatlas.com/skills/huytieu/weekly-checkin/)

The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.

Similar skills

Add this badge to your README

[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/huytieu/weekly-checkin/badge.svg)](https://modelsatlas.com/skills/huytieu/weekly-checkin/)

Questions about Weekly Checkin

What does the Weekly Checkin skill do?
Self-evolving second brain with 35 AI skills, 10 agents, and people CRM. Closed-loop harness: a V-model verification lifecycle where the worker never grades its own homework. Plus paired anti-slop design skills for marketing and product UI. Works with Claude Code, Cursor, Kiro, Gemini CLI, Codex.
Is Weekly Checkin safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Weekly Checkin access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (6ea1a6ff2160), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.