LLM Wiki
lewislulu/llm-wiki-skill
Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…
When the user wants to do a weekly review, check in on business progress, reflect on the week, plan next week's priorities, or says things like 'weekly review,' 'how did this week go,' 'what should…
$ npx skills add TheCraigHewitt/skills --skill weekly-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheCraigHewitt/skills weekly-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ceo/weekly-review .claude/skills/weekly-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "weekly-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/ceo/weekly-review into .claude/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TheCraigHewitt/skills/tree/main/ceo/weekly-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TheCraigHewitt/skills --skill weekly-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheCraigHewitt/skills weekly-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ceo/weekly-review .agents/skills/weekly-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "weekly-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/ceo/weekly-review into .agents/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill weekly-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheCraigHewitt/skills weekly-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ceo/weekly-review .cursor/skills/weekly-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "weekly-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/ceo/weekly-review into .cursor/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TheCraigHewitt/skills.git --path ceo/weekly-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TheCraigHewitt/skills --skill weekly-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheCraigHewitt/skills weekly-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ceo/weekly-review .gemini/skills/weekly-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "weekly-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/ceo/weekly-review into .gemini/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TheCraigHewitt/skills weekly-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TheCraigHewitt/skills --skill weekly-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ceo/weekly-review .github/skills/weekly-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "weekly-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/ceo/weekly-review into .github/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill weekly-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TheCraigHewitt/skills weekly-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ceo/weekly-review .opencode/skills/weekly-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "weekly-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/ceo/weekly-review into .opencode/skills/weekly-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
weekly-reviewWhen the user wants to do a weekly review, check in on business progress, reflect on the week, plan next week's priorities, or says things like 'weekly review,' 'how did this week go,' 'what should…
Weekly Review is an agent skill from TheCraigHewitt/skills. When the user wants to do a weekly review, check in on business progress, reflect on the week, plan next week's priorities, or says things like 'weekly review,' 'how did this week go,' 'what should I focus on next week,' 'end of week check-in,' 'Sunday review,' 'weekly retro.' A structured CEO operating rhythm in 15 minutes.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Knowledge Management, covering Journaling and reflection. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Weekly Review loads about 1.6k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 831 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 831 words, ~1,566 tokens.
.claude/skills/weekly-review/SKILL.md (or your agent's skills folder).You run a structured weekly check-in that takes 15 minutes and replaces the vague anxiety of "am I working on the right things?" with clarity. This is the CEO's operating rhythm — the one habit that compounds more than any other.
Check if BUSINESS_CONTEXT.md exists in the project root or current directory.
BUSINESS_CONTEXT.md.Also check if previous review files exist (look for reviews/ directory or files matching weekly-review-*.md). If found, read the most recent one to track continuity — did last week's priorities get done? Are recurring issues still unresolved?
Run through these sections conversationally. Don't dump a questionnaire — have a conversation where you ask, they answer, and you probe where it matters.
Ask for their key numbers this week. Keep it to 3-5 metrics that actually matter.
If you have their business context, prompt for the specific metrics they track. If not, ask:
"What are the 3-5 numbers you should know every week? Revenue, pipeline, churn, subscribers, whatever matters most."
For each metric:
Flag anything that moved more than 10% in either direction — that's worth discussing.
Ask: "What went well this week? What are you proud of, even if it's small?"
Founders are wired to focus on problems. Force them to name the wins. This isn't feel-good fluff — it's pattern recognition. Knowing what's working is as important as knowing what isn't.
Probe: "Why did that work? Is there a way to do more of it?"
Ask: "What didn't go well? What frustrated you? Where did you waste time?"
Then the important question: "What will you do differently next time?"
A loss without a lesson is just a bad week. A loss with a lesson is tuition.
If the same issue shows up in multiple reviews, flag it: "This is the third week you've mentioned [X]. Is this a symptom of something bigger we should address?"
Pull up their quarterly priorities from the business context (or ask what they are).
For each priority:
Then the hard question: "Did you spend the majority of your time this week on these priorities, or did other things eat your calendar?"
If they got pulled into reactive work, don't judge — help them see it. "What pulled you away? Is that going to keep happening? What would need to change?"
Ask: "If next week could only have 3 priorities, what are they?"
Three. Not five. Not "everything from this week plus three more things." Three.
For each priority:
Ask: "On a scale of 1-10, how's your energy? How are you feeling about the business right now?"
This isn't therapy. It's data. A founder at a 4 out of 10 three weeks in a row is heading for burnout, and no amount of strategy fixes that. If energy is low, ask what would help — is it a win they need, a decision they're avoiding, a person they need to hire, or just a day off?
After the conversation, generate a clean review document:
# Weekly Review — [Date]
## Scorecard
| Metric | This Week | Last Week | Trend | On Track? |
|--------|-----------|-----------|-------|-----------|
| [Metric] | [Value] | [Value] | [Up/Down/Flat] | [Yes/No/At Risk] |
## Wins
- [Win 1]
- [Win 2]
## Losses & Lessons
- **[Loss]:** [What happened] → **Lesson:** [What to do differently]
## Priority Progress
| Priority | Status | Notes |
|----------|--------|-------|
| [Priority 1] | [On track / At risk / Stalled] | [Brief note] |
## Next Week's Focus
1. **[Priority 1]** — Done = [definition]. First action: [specific action].
2. **[Priority 2]** — Done = [definition]. First action: [specific action].
3. **[Priority 3]** — Done = [definition]. First action: [specific action].
## Energy: [X/10]
[One sentence on what would help if below 7]Save to reviews/weekly-review-[YYYY-MM-DD].md if a reviews/ directory exists. If not, offer to create one.
© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in ceo/weekly-review of TheCraigHewitt/skills.
Open the folder on GitHubat commit fdbf39b
Weekly Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Weekly Review this skillTheCraigHewitt/skills | 159 | — | ~1.6k | Automated safety check: Pass | MIT | |
| LLM Wikilewislulu/llm-wiki-skill | 655 | — | ~3.7k | Automated safety check: Pass | None | |
| Munger Perspectivealchaincyf/munger-skill | 379 | 1 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Daily Journalhuytieu/COG-second-brain | 1.3k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Letterboxd Diaryjoe-bell/skills | 211 | — | ~4.2k | Automated safety check: Pass | MIT | |
| Em Grid Scorermanager-dot-dev/manager-skills | 114 | — | ~5.8k | Automated safety check: Pass | MIT |
lewislulu/llm-wiki-skill
Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…
alchaincyf/munger-skill
查理·芒格的思维框架与表达方式。基于《穷查理宝典》、伯克希尔/Daily Journal股东会、 USC/哈佛演讲、访谈记录、外部批评等50+来源的深度调研, 提炼5个核心心智模型、8条决策启发式和完整的表达DNA。
huytieu/COG-second-brain
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself.
joe-bell/skills
Fetch recently watched films from a Letterboxd member's diary RSS feed and render them as a compact markdown list, with first-run setup for the username.
manager-dot-dev/manager-skills
Score an Engineering Manager's coverage across all 12 cells of the EM Grid based on their calendar and Slack.
foryourhealth111-pixel/Vibe-Skills
This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content…
TheCraigHewitt/skills
Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.
TheCraigHewitt/skills
When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.
TheCraigHewitt/skills
Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.
TheCraigHewitt/skills
When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.
TheCraigHewitt/skills
When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.
TheCraigHewitt/skills
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.
Categories
When the user wants to do a weekly review, check in on business progress, reflect on the week, plan next week's priorities, or says things like 'weekly review,' 'how did this week go,' 'what should…. Weekly Review is an agent skill from TheCraigHewitt/skills.' A structured CEO operating rhythm in 15 minutes.
Weekly Review fits situations like: wants to do a weekly review; check in on business progress; reflect on the week; plan next weeks priorities.
Run `npx skills add TheCraigHewitt/skills --skill weekly-review -a claude-code`. Or copy the skill folder (ceo/weekly-review in TheCraigHewitt/skills) into .claude/skills/weekly-review in your project. Claude Code loads it when a task matches its description.
Run `npx skills add TheCraigHewitt/skills --skill weekly-review -a codex`. Or copy the skill folder (ceo/weekly-review in TheCraigHewitt/skills) into .agents/skills/weekly-review in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill weekly-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/weekly-review, .gemini/skills/weekly-review, .github/skills/weekly-review and .opencode/skills/weekly-review in your project.
SKILL.md names no scripts, command-line tools or credentials: Weekly Review is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Weekly Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Weekly Review: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), Munger Perspective (alchaincyf/munger-skill, 379 stars), Daily Journal (huytieu/COG-second-brain, 1.3k stars) and Letterboxd Diary (joe-bell/skills, 211 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.
Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.