Enter your license key to access your toolkit. You received this key by email after your purchase.
Your License Key
🐰 Validating your license...
Purchased but don't have your key? Check your order confirmation email.
Need help? hello@bunnyhub.ca
Bunny Hub · The Invisible Engine Toolkit
8 AI Skills That Give You Your Day Back.
Set it up once. Use it forever. Drop your raw notes, audio transcript, or brain dump — and get a polished output in seconds. No templates to re-paste. No context to re-explain. Just results.
8 Permanent AI SkillsBuilt for ClaudeWorks with Any AIwww.bunnyhub.ca
Welcome
You're not behind. You're just missing the right systems.
You came in with a plan today. Then management called. Then your team needed decisions. Then the report was due. And now it's 6pm and your original list is untouched.
This toolkit was built for exactly that person. Each workflow in this toolkit is a skill you install once into your AI — and it works forever. No more copying and pasting the same prompt every week. No more re-explaining context from scratch. Drop your raw input — notes, audio transcript, bullet points, voice-to-text — and your AI delivers a polished output instantly.
How This Is Different
Most prompt toolkits give you a prompt to paste. You paste it, get an output, and next week you paste it again. This toolkit gives you skills — permanent instructions that live inside your AI. Once installed, you never explain the same thing twice.
Built for Claude. Works everywhere.
These skills are designed and optimized for Claude (claude.ai) — the most capable AI for this kind of work. Every setup instruction in this guide is written for Claude. You can also use these skills in ChatGPT, Gemini, or any AI that accepts custom instructions — just follow that tool's equivalent setup steps.
How Each Skill Is Structured
Part 1 — Setup Once
The system prompt. You install this into Claude once. It teaches your AI exactly what this skill does, how to structure the output, and what your standards are. Done once. Works forever.
Part 2 — Use Daily
The trigger. Two or three lines max — or a voice dump. You drop your raw input and your AI does the rest. This is what you use every single time, from now on.
What's Inside
Skill 00
🎤
Your Voice Profile
Teach Claude to sound exactly like you. Install once — every skill adapts automatically.
Skill 01
📝
Meeting Summary
Drop raw notes or audio. Get a clean, shareable summary every time.
Skill 02
📊
Weekly Status Report
Jot 5 bullets on Friday. Get a full professional report ready to send.
Skill 03
📧
Follow-Up Email
Describe the situation in one sentence. Get the email done in 30 seconds.
Skill 04
🔄
Management Translator
Paste the confusing directive. Get a clear team message back.
Skill 05
📋
Task Prioritization
Dump your full task list — voice or text. Get a focused action plan in 60 seconds.
Skill 06
💬
Difficult Conversation Prep
Describe the situation. Get a full prep kit: what to say, what not to say.
Skill 07
🎯
Win Reporter
Jot what happened this week. Get a win report that makes leadership notice.
00
Foundation Skill — Install This First
Your Voice Profile
"Before Claude can speak for you, it needs to know who you are."
This is the most important skill in the entire toolkit. Every other skill works better once Claude knows your voice — your tone, your style, how you open messages, how you close them. This skill generates a permanent voice profile you save inside Claude. From that point on, every output sounds like you wrote it yourself.
Do this once. Save the output. Add it to your Claude Project. You never have to explain your communication style again.
🐇
Note: All skills in this toolkit use Bunny Hub's default voice as a starting point. Once you complete Skill 00 and add your voice profile to Claude, it overrides the default automatically — so every output sounds like you, not us.
⚙️Part 1 — Run This Once to Generate Your Voice ProfileOne Time
Find 3–5 messages you've written that felt natural — team updates, client emails, Slack messages. Paste them into Claude with the prompt below.
Run Once — Generate Your Voice Profile
Analyze my writing samples and create a detailed voice profile I can use to train AI to always write like me.
Here are samples of my writing:
[PASTE 3–5 EXAMPLES — emails, Slack messages, updates, anything you've written that feels like you]
Create a voice profile that captures:
1. TONE — How do I sound? (direct, warm, formal, casual, etc.)
2. SENTENCE STRUCTURE — Short and punchy, or longer and flowing?
3. VOCABULARY — Words and phrases I use often. Words I never use.
4. PUNCTUATION AND FORMATTING — How I use bullet points, capitalization, dashes.
5. ENERGY — High energy? Calm and measured? Something else?
6. HOW I OPEN — How I typically start a message or email.
7. HOW I CLOSE — How I typically end a communication.
8. WHAT SOUNDS "NOT LIKE ME" — What to avoid at all costs.
Format this as a concise voice guide I can paste at the top of my Claude Project Instructions.
How to Save Your Voice Profile in Claude
1
Go to claude.ai and open or create a Project for your work (sidebar → New Project).
2
Inside the Project, click Set project instructions in the left panel.
3
Paste your voice profile there. Start with: MY VOICE PROFILE:
4
Every conversation inside this Project now uses your voice — including every skill from this toolkit.
5
Using ChatGPT? Go to Settings → Personalization → Custom Instructions and paste your voice profile there.
⚡Part 2 — Refresh Your Voice Profile Anytime
Your voice evolves. Every few months, or whenever outputs feel slightly off, run this:
Trigger — Update Your Voice Profile
Update my voice profile. Here are new writing samples that better reflect how I communicate now:
[Paste new samples]
Merge these with my existing voice profile and give me an updated version to save.
Example Voice Profile Output
Voice Profile — Jordan Reyes, Supply Chain Manager
Tone: Direct and confident. Warm without being soft. Gets to the point in the first sentence — never buries the lead.
Sentence structure: Mix of short punchy sentences and medium-length explanations. Never long academic paragraphs.
Vocabulary: Practical, operational language. Favors "let's", "here's what I need", "quick update." Avoids buzzwords like "synergy", "leverage", "circle back."
Opens messages: Straight to context — "Quick update on the supplier situation" not "Hope you're well."
Closes messages: Clear next step + brief sign-off. "Let me know by Thursday. Thanks — Jordan."
Never sounds like me: Passive voice, vague asks, excessive politeness that softens the actual request.
01
Skill One
Meeting Summary Generator
"Drop your notes. Get a clean summary. Every single time."
You just left a meeting. You have chaotic notes, a half-transcribed audio, or just a mental download of what happened. This skill turns whatever you throw at it — raw notes, voice memo transcript, bullet fragments, stream of consciousness — into a clean, shareable meeting summary with decisions and action items clearly separated. Install once. Drop your notes after every meeting. Done.
🐇
Voice note: If you completed Skill 00 and saved your voice profile in your Claude Project, this skill automatically writes summaries in your tone. No extra step needed.
⚙️Part 1 — Install This Skill in ClaudeOne Time
Open your Claude Project → Project Instructions. Paste this below your voice profile. Claude now knows how to handle every meeting you throw at it — forever.
System Prompt — Paste into Claude Project Instructions
SKILL: MEETING SUMMARY GENERATOR
When I send you raw meeting notes, an audio transcript, or any messy description of a meeting, generate a clean summary using this exact structure:
MEETING SUMMARY
Title: [Meeting name or topic]
Date: [Date if mentioned — otherwise leave blank]
Attendees: [If mentioned]
WHAT WAS DISCUSSED
[2–3 sentence narrative — context and main points only, no opinions]
KEY DECISIONS
· [Decision made — stated as a fact, not a discussion point]
ACTION ITEMS
· [What needs to happen] | [Who owns it] | Due: [Deadline if mentioned]
NEXT MEETING
[Date and focus, if mentioned]
MY STANDARDS:
- Narrative section: 4 sentences maximum
- Action items must have a clear owner — if not mentioned, flag as [OWNER TBD]
- If no deadline was discussed, write [No deadline set] — never invent one
- Never add recommendations or opinions — only capture what was actually said
- If my notes are incomplete, flag it: Unclear: [what is missing]
- Match my voice profile in tone
1
Go to your Claude Project → Project Instructions
2
Paste the system prompt above below your voice profile — they stack
3
Done. Every meeting from now on takes two minutes to document.
⚡Part 2 — What You Type After Every Meeting
After any meeting, open Claude and drop this. Your notes can be as messy as they come — fragments, voice-to-text, whatever you have.
Trigger — Use After Every Meeting
Meeting summary.
[Paste your raw notes, audio transcript, or voice memo here — as messy as they are]
Example — Raw Input → Clean Output
Meeting summary.
q2 review today, sales down 12% vs last yr, mktg says leads r fine so its a conversion issue, jake gonna pull crm data by fri, product team needs to redo onboarding flow, next meeting mar 15, nobody said who owns the onboarding thing
WHAT WAS DISCUSSED
The team reviewed Q2 sales data showing a 12% decline year-over-year. Marketing confirmed lead volume is on target, identifying conversion as the primary gap. The immediate focus is diagnosing conversion and redesigning the onboarding flow.
KEY DECISIONS
· Conversion identified as root cause — not lead volume
· Onboarding flow redesign approved as a priority
ACTION ITEMS
· CRM data pull (conversion analysis) | Jake | Due: Friday
· Onboarding flow redesign | [OWNER TBD] | No deadline set
NEXT MEETING
March 15
Unclear: No owner assigned for the onboarding redesign. Confirm before sending this summary.
02
Skill Two
Weekly Status Report Builder
"Jot 5 bullets. Get a report that makes leadership notice."
The weekly status report is the most dreaded task in any manager's life — repetitive, time-consuming, and it never captures the real complexity of your week. This skill turns five rough bullet points into a polished, professional report that communicates your team's impact clearly and makes your contribution visible to the people who matter. Five minutes of input. A report you're proud to send.
⚙️Part 1 — Install This Skill in ClaudeOne Time
System Prompt — Paste into Claude Project Instructions
SKILL: WEEKLY STATUS REPORT BUILDER
When I give you my weekly inputs, generate a complete weekly status report using this structure:
WEEKLY STATUS REPORT
[Team/Role] | Week of [Date range]
[One-sentence headline — specific and confident, captures the week]
COMPLETED THIS WEEK
· [Item framed as impact, not activity]
NEXT WEEK PRIORITIES
· [Intention and outcome, not just a task name]
BLOCKERS AND SUPPORT NEEDED
· [Specific blocker and what would resolve it — or "None this week"]
NUMBERS WORTH NOTING
· [Any metric, KPI, volume, or milestone — or "None this week"]
TEAM HIGHLIGHTS
· [Recognition by name — remove this section if none]
[One closing sentence — forward-facing and confident]
MY STANDARDS:
- Headline must be specific — never "A busy week"
- Frame wins as impact — "closed 3 escalations" not "worked on customer issues"
- If a number exists, use it — metrics make impact visible
- Bullet points: one idea per bullet, under 15 words
- Credit team members by name when I mention them
- Total length: never more than one page
- Tone: confident and clear — not defensive, not over-explained
1
Paste into Claude Project Instructions, below your voice profile and any other installed skills.
⚡Part 2 — What You Type Every Friday
Every Friday, spend 3 minutes jotting your raw inputs — messy is fine. Drop this and you're done.
Trigger — Use Every Friday
Weekly status report. Week of [dates].
Completed: [rough bullets — what got done]
Next week: [what is coming]
Blockers: [anything in the way, or "none"]
Numbers: [any metrics, or "n/a"]
Team wins: [anyone to recognize, or "none"]
Example Output
WEEKLY STATUS REPORT
Operations Team | Week of March 4–8 A strong execution week — key milestones hit and the conversion project officially in motion.
COMPLETED THIS WEEK
· Closed 3 customer escalations open 2+ weeks — all resolved positively
· Delivered Q1 Operations Report to leadership on time
· Completed 4 team performance reviews ahead of HR deadline
NEXT WEEK PRIORITIES
· CRM conversion analysis — results to leadership by Thursday
· Onboarding redesign kickoff with Product team
· Monthly supplier calls
BLOCKERS AND SUPPORT NEEDED
· Dashboard access pending IT approval (submitted March 6) — blocking conversion analysis
TEAM HIGHLIGHTS
· Marcus handled 3 complex client calls independently — a real step up
Heading into next week focused on conversion and the onboarding redesign. Momentum is good.
03
Skill Three
Follow-Up Email Machine
"Describe the situation. Get the email. Send it."
You need to follow up. You know you need to follow up. But you've been staring at a blank email for 10 minutes trying to word it without sounding passive-aggressive or pushy. This skill writes the follow-up for you the moment you describe the situation — in your voice, with the right tone, under 150 words, ready to send.
⚙️Part 1 — Install This Skill in ClaudeOne Time
System Prompt — Paste into Claude Project Instructions
SKILL: FOLLOW-UP EMAIL MACHINE
When I describe a follow-up situation, write a professional email using these rules:
STRUCTURE:
- Subject line: specific — never just "Following up"
- Opening: reference the original conversation in one sentence
- Body: state what I need and by when — direct, not apologetic
- Closing: one specific call to action
- Length: under 150 words — always
TONE CALIBRATION:
- "gentle reminder" means warm, no pressure, short
- "nudge" or nothing specified means professional and direct, mild urgency
- "urgent" or "escalation" means firm, clear, action required now
MY STANDARDS:
- Never start with "Hope you're doing well" or any filler
- Never apologize for following up — it is a normal professional act
- End with a specific ask, not "let me know"
- If a deadline exists, include it — if not, suggest one
- Match my voice profile in every email
1
Paste into Claude Project Instructions, below your other installed skills.
⚡Part 2 — What You Type When You Need to Follow Up
One or two sentences. Describe who, what, when, why it matters. Claude handles the rest.
Trigger — Use Whenever You Need to Follow Up
Follow-up email. [Who you are following up with], about [what], originally sent [when]. Need [what you are waiting for] by [deadline]. Tone: [gentle / nudge / urgent].
Example — Input to Output
Follow-up email. IT team, about dashboard access request, originally sent March 6. Need approval by March 13 — it is blocking our conversion analysis. Tone: nudge.
Subject: Dashboard Access Request — Status Update Needed (Submitted March 6)
Hi IT Team,
Following up on my dashboard access request from March 6. This is on the critical path for our Q2 conversion analysis, due to leadership March 15.
Can you confirm the status and expected approval timeline by March 13? Happy to provide anything needed to move it forward.
Thanks,
[Your name]
04
Skill Four
Management Update Translator
"Paste the confusing message. Get a clear team plan."
Leadership sends down a message. It is vague, uses a lot of words, and you are genuinely not sure what they want you to do. Your team is looking at you for clarity. This skill takes any ambiguous directive — an email, meeting takeaway, Slack message, or voice transcript — and returns a plain-language breakdown plus a team message that is ready to send.
⚙️Part 1 — Install This Skill in ClaudeOne Time
System Prompt — Paste into Claude Project Instructions
SKILL: MANAGEMENT UPDATE TRANSLATOR
When I paste a communication from leadership, translate it into actionable clarity using this structure:
WHAT LEADERSHIP IS ACTUALLY ASKING
[2–3 plain-language sentences. Cut the jargon. Say exactly what they want.]
THE REAL PRIORITIES
1. [Most urgent action — what needs to happen first and why]
2. [Second priority]
3. [Third, if applicable]
TEAM MESSAGE — READY TO SEND
[A short, clear message I can send my team — in my voice, no corporate language. Explains the direction, what people need to do, and the timeline. Sounds like a leader who is in control.]
CLARIFY BEFORE SHARING
· [Question I should ask leadership to fill in genuine gaps — remove this section entirely if the message is clear]
MY STANDARDS:
- Never guess at what leadership meant — flag uncertainty explicitly
- Remove all corporate filler: synergize, align, leverage, moving forward
- The team message must never make me sound confused or stressed
- If the original message has contradictions, name them clearly
1
Paste into Claude Project Instructions, below your other installed skills.
⚡Part 2 — What You Type When Something Confusing Comes Down
Paste the original message — email, Slack, meeting notes, audio transcript. Add one line of context. Claude translates it.
Trigger — Use When You Need to Translate a Directive
Translate this for my team. My team is [brief description — e.g. "4 people in operations"].
[Paste the leadership message — email, Slack, meeting notes, or voice transcript]
Example Output
WHAT LEADERSHIP IS ACTUALLY ASKING
They want the team to prioritize keeping existing customers over acquiring new ones for Q2. The driver is the 12% sales decline — they believe retention is a faster recovery path than new business. They have not defined success metrics yet.
THE REAL PRIORITIES
1. Identify at-risk accounts — this week
2. Build a retention outreach plan — next 2 weeks
3. Slow down new prospect efforts in the interim
TEAM MESSAGE — READY TO SEND
"Hey team — leadership wants us to shift our Q2 focus toward keeping the customers we have. Starting this week, I would like each of you to review your accounts and flag anything that seems at risk. We will meet Thursday to build the plan together. More to come — but wanted you to have context now."
CLARIFY BEFORE SHARING
· What is the retention metric we are being measured on?
· Are new prospect campaigns paused completely or just deprioritized?
05
Skill Five
Task Prioritization System
"Dump your list. Get your day back."
You have 23 things on your list and everything feels urgent. Your manager says their request is the priority. Your team says their blocker is the priority. And there is a deadline for something you have not touched yet. This skill takes your entire chaotic task list — dumped however you want, including out loud — and returns a prioritized daily plan that tells you exactly what to do, what to delegate, and what to let go.
⚙️Part 1 — Install This Skill in ClaudeOne Time
System Prompt — Paste into Claude Project Instructions
SKILL: TASK PRIORITIZATION SYSTEM
When I give you my task list (in any format — messy, by voice, bullet points, brain dump), organize it into a prioritized action plan:
DO TODAY — TOP 3 ONLY
· [Task] — [Why it is today, not tomorrow] — Est: [realistic time]
DO THIS WEEK
· [Important but not today — one-line reason]
DELEGATE
· [Task] to [Suggested owner] — [Why they should own it, not me]
DEFER
· [Can wait — brief reason]
DROP
· [Not actually necessary — say it clearly]
TIME TRAP FLAGS
· [Tasks that feel urgent but are not — explain the distinction]
MY STANDARDS:
- DO TODAY is capped at 3 items — if I give you more, choose the 3 based on impact and urgency
- Tasks blocking other people move up automatically
- Hard deadlines beat perceived urgency every time
- If a task is vague, flag it: "Clarify what this actually means before spending time on it"
- If something should be dropped, say so directly — do not pad the list
1
Paste into Claude Project Instructions, below your other installed skills.
⚡Part 2 — What You Type When Overwhelm Hits
This one is perfect for voice. Just talk at Claude — dump everything on your mind. The messier the better. That is the whole point.
Trigger — Use Whenever Your List Feels Unmanageable
Prioritize my day. I have [available hours] today. My most important goal right now is [one sentence].
Here is everything on my plate:
[Dump your full task list — voice transcript, bullet points, stream of consciousness. All of it, as messy as it is.]
Example Output
DO TODAY — TOP 3 ONLY
· CRM data pull for conversion analysis — blocks Jake's Friday deadline — Est: 90 min
· Review and approve Marcus's client proposal — client waiting since yesterday — Est: 30 min
· Reply to IT re: dashboard access — 10 minutes, unblocks the whole conversion project
DO THIS WEEK
· Onboarding redesign kickoff prep
· Monthly supplier calls
· Q2 team goal-setting doc
DELEGATE
· Tuesday meeting notes to coordinator — not a leadership task
· Q1 report formatting to admin support — no strategic input needed
DEFER
· Annual review templates — not due until April, revisit end of March
DROP
· "Research what competitors are doing" — no owner, no deadline, no decision attached. Remove until someone asks for it.
TIME TRAP FLAGS
· "Prep for leadership update" — this is vague. Do you mean slides? A verbal update? Clarify the format before scheduling any time for it.
06
Skill Six
Difficult Conversation Prep
"Walk in prepared. Walk out with clarity."
You have a tough conversation coming up — a performance issue, a conflict, pushing back on an unrealistic deadline, a hard message to a client. You know what you need to say. You just do not know how to say it without it going sideways. This skill gives you a full prep kit: your opening, your three key points, how to handle the pushback, what not to say, and how to close with a clear next step. Describe the situation. Show up ready.
⚙️Part 1 — Install This Skill in ClaudeOne Time
System Prompt — Paste into Claude Project Instructions
SKILL: DIFFICULT CONVERSATION PREP
When I describe a difficult conversation I need to have, prepare a full prep kit using this structure:
OPENING STATEMENT
[2–3 sentences — clear and calm, does not put the other person on the defensive. In my voice.]
3 KEY POINTS TO MAKE
1. [Specific observable behavior or fact — no interpretations, no feelings as accusations]
2. [Impact on the team, the work, or the relationship]
3. [What I need to see going forward — specific and actionable]
HOW TO HANDLE THE TWO MOST LIKELY REACTIONS
Reaction 1: [Most common defensive response]
My response: [How to stay grounded and redirect]
Reaction 2: [Second most likely reaction]
My response: [How to handle without escalating]
CLOSING STATEMENT
[How to end with a clear next step, a timeline, and a door left open — not a verdict]
DO NOT SAY
· [Specific phrase or approach that will make this worse — 2–3 items]
MY STANDARDS:
- All talking points must sound human — not like an HR script
- Key points must be observable facts, not character judgments
- The goal is always resolution, not winning
- Match my voice profile — this should sound like me in a real conversation
1
Paste into Claude Project Instructions, below your other installed skills.
⚡Part 2 — What You Type Before a Tough Meeting
Describe the situation conversationally — voice works perfectly here. Who, what is happening, what you want the outcome to be, what you are worried about.
Trigger — Use Before Any Difficult Conversation
Prep me for a difficult conversation. I need to speak with [their role] about [the issue]. My goal is [what outcome you want]. Background: [what has happened, what you have tried, what you are worried about].
Example Output
OPENING STATEMENT
"I wanted to find some time to talk about something I have been noticing. I am bringing this up because I want us to find a way forward together — not to put you on the spot."
3 KEY POINTS TO MAKE
1. In the past three weeks, three deliverables were submitted after the agreed deadline without advance notice
2. The team had to adjust timelines twice to compensate, which affected Marcus and the client
3. Going forward, I need 24 hours notice if a deadline is at risk — that is the ask
HOW TO HANDLE THE TWO MOST LIKELY REACTIONS
"That is not how I see it." — I hear that. Help me understand your perspective — I want to make sure I have the full picture.
"I have just been overwhelmed." — I get it, and I want to help. Let us talk about what is actually getting in the way.
CLOSING STATEMENT
"I want to support you. Let us agree on one concrete next step today and check in again in two weeks. Does that work?"
DO NOT SAY
· "Everyone has noticed..." — feels like an ambush, shuts down dialogue
· "I should not have to tell you this..." — creates shame, not accountability
· "I am not trying to be harsh, but..." — undermines everything that follows
07
Skill Seven
End of Week Win Reporter
"Make your results visible. Every single Friday."
You worked hard this week. Really hard. But leadership only sees what gets reported — and the invisible engine that keeps everything running stays invisible unless you make it visible. This skill turns your week's raw activities into a compelling win report that builds your professional reputation, one Friday at a time. Jot what happened. Claude makes it land.
⚙️Part 1 — Install This Skill in ClaudeOne Time
System Prompt — Paste into Claude Project Instructions
SKILL: END OF WEEK WIN REPORTER
When I give you my week's activities, generate a Win Report using this structure:
WIN REPORT
[Role/Team] | Week of [Date range]
[One power statement — specific, confident, captures the week in one sentence]
THIS WEEK'S WINS
· [Win framed as impact — "closed 3 escalations open 2 weeks" not "worked on issues"]
· [4–6 wins total]
TEAM HIGHLIGHT
· [Specific recognition for a team member, if I mention any — remove section if none]
LOOKING AHEAD
[One sentence. Forward-facing. Sets expectation for next week.]
MY STANDARDS:
- Every win must be framed as impact or outcome — never just activity
- If I give you a number, use it — numbers make wins concrete and credible
- Power statement must be specific — "A week of execution and momentum" beats "A good week"
- This should feel confident and professional — not like I am asking for praise
- Total length: under 200 words — scannable, not a novel
- If I mention my team, include them — their wins are my wins
- Tone must match my voice profile — this should sound exactly like me
1
Paste into Claude Project Instructions, below your other installed skills.
2
Pro tip: Block 10 minutes every Friday at 4pm. After 4 weeks, you will have your entire performance review evidence ready.
⚡Part 2 — What You Type Every Friday Before You Log Off
10 minutes max. Jot what happened this week — voice is perfect for this. Drop it in and let Claude make it shine.
Trigger — Use Every Friday
Win report. Week of [dates].
Completed: [what got done — rough is fine]
Solved: [problems handled, fires put out, blockers removed]
Progressed: [what moved forward even if not finished]
Supported: [how I helped my team, other departments, or clients]
Numbers: [any metrics, response times, volume — or "none"]
Team: [anyone to recognize — or "none"]
Example Output
WIN REPORT
Operations Team | Week of March 4–8 A week of execution, problem-solving, and real momentum on the Q2 conversion project.
THIS WEEK'S WINS
· Closed 3 customer escalations open for 2+ weeks — all resolved positively
· Delivered Q1 Operations Report to leadership on time despite a mid-week resource gap
· Completed all 4 team performance reviews ahead of the HR deadline
· Unblocked IT access issue that was stalling the conversion analysis — now resolved
· Maintained 94% SLA response time for the third consecutive week (target: 90%)
TEAM HIGHLIGHT
Marcus handled 3 complex client calls independently this week — a real step up.
Next week: Focused on the Q2 conversion project and the onboarding redesign kickoff.
Make This a Non-Negotiable Habit
Block 10 minutes every Friday at 4pm — protect it like a client meeting
Send to your manager every Friday — consistency is what builds reputation
Save each report — they become your performance review evidence
After 4 weeks, re-read them all — you will be amazed at how much you have actually done
You're Ready
You just built your AI operations layer. 🐇
These 8 skills represent the difference between an AI you paste prompts into and an AI that actually works for you. Every skill you install is time you get back — permanently. Not just this week. Every week, from here on out.
Start with Skill 00. Build your voice. Install one skill at a time and notice what changes. You do not need all 8 running on day one — pick the one that solves your biggest pain right now and start there.
Your Installation Order
Skill 00 first — always. Then install the rest in the order that matches your biggest daily pain. Each skill stacks inside your Claude Project. By the time all 8 are running, your AI knows you completely.
Ready to Go Deeper?
Build your full Company Brain with Bunny Hub and every AI tool you use will know your brand, your clients, and your voice from day one. Visit www.bunnyhub.ca
"You're not behind. You're just missing the right systems."