القائمة
Interview-based blog post creation that shares hard-won lessons through storytelling. Use when crafting posts about personal learnings, best practices, or experience-based insights.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Bootstraps a new project directory with base configuration files, MCP servers, API connections, and template skills from OutworkOS. Use when setting up a new project, initializing a workspace, or configuring MCP integrations for a new directory.
Gain-based weekly reflection. Looks backward at what moved forward across all projects, written as narrative prose. Modeled on The Gap and The Gain — measures progress against where you were, not where you wish you were.
Composes, drafts, and sends emails via Gmail. Enforces natural writing style (no em dashes, no AI tells), proper threading, and correct signature handling. Use whenever drafting, replying to, or sending any email.
"Produces a meeting prep briefing for upcoming calendar meetings by researching attendees, email history, past meetings, and company backgrounds. Use when the user asks to prepare for meetings, prep for tomorrow, review upcoming meetings, get ready for a meeting day, or asks 'what meetings do I have'. Also use when the user asks to research a specific meeting or contact before a call."
"Cross-project inbox scan — cleans noise, routes signals to projects, creates Todoist tasks for gaps, and ranks priorities by time block. Replaces /triage, /inbox-zero, and /sitrep."
Generates Spotify playlists using MCP spotify tools. Use when user wants to create a playlist based on mood, genre, similar artists, or any theme. Handles auth, track discovery, playlist creation, and adding tracks.
| name | blog-writing-from-experience |
| description | Interview-based blog post creation that shares hard-won lessons through storytelling. Use when crafting posts about personal learnings, best practices, or experience-based insights. |
This skill helps craft blog posts that share hard-won lessons and best practices through personal storytelling. The writing is exploratory, humble, and experience-based - not prescriptive, but invitational.
The goal is to understand the lessons and the experiences that led to them. Ask one question at a time, building on responses.
Essential elements to uncover:
Interview technique:
Work section by section, showing each draft and getting feedback before proceeding.
Structural flexibility:
Draft iteratively:
After drafting:
Look for opportunities to:
Before finalizing, verify the post maintains these principles:
Offer to interview the user to understand their lessons and experiences. One question at a time, building context as you go.
Once you understand the content, propose a structure based on what you've learned. Get their input on the approach before writing.
When all sections are approved, compile into a complete post. Consider offering to create supporting materials (social posts, image prompts) if relevant.
Topic: User wants to write about lessons learned from managing remote teams
Interview flow:
Claude: What's the primary audience for this post? Who are you trying to help?
User: First-time managers who just inherited remote teams and are struggling
Claude: What specific problem are they facing that prompted you to want to write this?
User: They're trying to apply in-person management tactics and it's backfiring
Claude: Can you share a specific example of a tactic that backfired for you?
User: I used to schedule daily standups at 9am thinking it would keep everyone aligned...
Claude: What happened? How did you realize it wasn't working?
User: [Describes the failure and what they learned]
Claude: What do you do now instead?
User: [Shares specific approach with details]
Claude: Can you walk me through exactly how that works? Like what does a typical week look like?
User: [Provides concrete implementation details]
Opening might look like:
Two years ago, I took over my first remote team. I did what seemed obvious: scheduled daily 9am standups to keep everyone aligned. Within a month, I noticed people were showing up but not really showing up - cameras off, minimal updates, energy flat. The problem wasn't the team. It was that I was managing remote people like they were sitting in an office.
Lesson section might include:
What I do now: I replaced synchronous check-ins with async updates in Slack. Each Monday, everyone posts their weekly plan. Thursday, they share progress and blockers. Takes 5 minutes to write, I read them over coffee, and we only meet when there's an actual decision to make.
Why it matters: This respects that my team spans 6 time zones. The person in Sydney doesn't need to stay up until midnight to tell me they're on track. And I've noticed the written updates are actually more thoughtful than what people said in standups.
When I skip it: If there's a crisis or we're kicking off something complex, we'll do a live session. But that's the exception, not the default.
Closing might ask:
What's worked for you in managing remote teams? Have you found ways to build connection without defaulting to more meetings? I'm especially curious how others handle the balance between async work and real-time collaboration.
This is about helping the user articulate what they've learned through experience and iteration. The blog post should feel like a conversation with someone sharing their journey, not an expert handing down wisdom.
Key mindsets:
The reader experience should be:
Different topics will organize differently: Some posts might group lessons thematically, others chronologically, others by problem severity. Some benefit from a TL;DR, others from narrative unfolding. The principles stay constant - grounded in experience, specific, exploratory, invitational - but the structure emerges from the content.