القائمة
Generate exec-level status updates using the 5 Levels of Communicating Impact framework
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Analyze the current or a past Claude Code session to extract knowledge worth persisting to the vault. Proposes items, you pick, it writes them to the right place. This skill activates when you say capture this session, what should we save, what did we learn, or at end-of-session when valuable knowledge was generated.
One-time setup wizard — personalize the vault with your name, domains, and preferences
Hands-on guided tour of the vault — learn by doing with real examples
Migrate content from staging, chunk large files, and handle bulk note reorganization
Transform and organize notes in the Obsidian vault — add frontmatter, detect note types, create relationships
Extract URL content and create literature notes and review notes from web articles
| name | weekly-status |
| description | Generate exec-level status updates using the 5 Levels of Communicating Impact framework |
| activation | ["weekly status","weekly update","status update","highlights and priorities"] |
Generate exec-level status updates using the 5 Levels of Communicating Impact framework.
Ask the user:
How do you want to start?
1. **I have a draft/idea** — paste what you're thinking and I'll help shape it
2. **Let's check my tasks** — I'll look at Tasks.md and we'll identify highlights together
If option 1: Take their draft and skip to Step 3 (Draft & Refine).
If option 2: Continue to Step 2.
Tasks.md for completed items this weekPresent what you found:
From your Tasks.md, here's what got done this week:
- [item 1]
- [item 2]
...
Which of these should be highlights? Anything missing?
Write a first draft:
Apply 5 Levels thinking internally — aim for Level 3-5 statements (metrics, goals, business impact) but don't be formulaic about it. The output should read naturally.
Present the draft:
Here's a draft:
# Top 5 Highlights
- **[Thing 1]** — [impact statement] [@collaborators]
- ...
# Top 5 Priorities
- [next week item]
- ...
---
What would you change? Too long? Missing something? Wrong emphasis?
Refine based on feedback. Keep iterating until the user approves.
Common adjustments:
Provide the final status update ready to paste.
Do:
Don't:
Length: ~3-5 lines per highlight max. If it needs more, it's probably two highlights.
Use this internally to level up statements:
| Level | Focus | Example |
|---|---|---|
| 1 | What you did | "Fixed the bug" |
| 2 | Had impact | "Reduced errors" |
| 3 | Specific (metrics) | "Reduced errors by 40%" |
| 4 | Tied to goal | "Hit Q1 reliability target" |
| 5 | Business impact | "Prevented $2M revenue loss" |
Aim for Level 3+ but write naturally, not like a template.