Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Defines professional positioning including unique value proposition, target audience, platform selection, content themes, and a 90-day visibility plan. Produces a complete brand strategy document.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
339 lines · 2,686 words
User wants to build or refine their professional personal brand
User asks how to become known for their expertise
User wants a plan for increasing professional visibility
User needs a content strategy tied to career growth
Defines professional positioning including unique value proposition, target audience, platform selection, content themes, and a 90-day visibility plan. Produces a complete brand strategy document.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Personal Brand Strategy skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
What it covers
When to Use
Process
Output Format
Rules
Edge Cases
Example
Personal Brand Strategy: Data Engineer
User asks about thought leadership or establishing authority in their field
Do NOT use when: user wants LinkedIn profile text written (use linkedin-summary-writer), user needs a resume (use resume-bullet-writer), user wants business-level social media marketing (use content marketing skills)
Gather professional identity inputs. Collect the foundation for the brand:
Current role, industry, and years of experience
2-3 areas of deepest expertise or knowledge
Career goal for the next 1-3 years (promotion, career change, consulting, speaking, hiring)
What the user wants to be known for (the "go-to person for X" statement)
Current online presence (LinkedIn, personal site, social media, none)
Time available per week for brand-building activities (1 hour, 3 hours, 5+ hours)
Define the unique value proposition (UVP). Craft the core positioning statement:
Intersection formula: [Expertise Area 1] + [Expertise Area 2] + [Unique Perspective] = UVP
The UVP must be specific enough to differentiate from thousands of others in the same field
Test: "I help [target audience] with [specific problem] by [unique approach]"
Identify 2-3 proof points that validate the UVP (achievements, results, experience)
Identify the target audience. Define who the brand is for:
Primary audience: the people whose attention matters most for the career goal
Secondary audience: peers and community members who amplify the message
What problems does the target audience face that the user can address?
Where does the target audience spend time online?
What format does the target audience prefer (long-form articles, short posts, video, podcasts)?
Select platforms. Choose 1-2 primary platforms based on audience and capacity:
LinkedIn: best for B2B, professional services, corporate careers, consulting
Personal blog or newsletter: best for deep expertise, thought leadership, SEO
Industry-specific communities: best for niche expertise and peer recognition
Evaluate each platform on: audience presence, content format fit, time investment, discoverability
Do NOT recommend spreading across 4+ platforms -- focus beats coverage
Define content themes. Build a content pillar system:
3-4 content pillars (recurring themes) aligned with the UVP
For each pillar: 5-7 specific topic ideas the user can create content about
Content mix: 60% educational (teaches something), 25% perspective (opinion or insight), 15% personal (story or experience)
Format recommendations per pillar (written post, carousel, case study, how-to)
Build the 90-day visibility plan. Create a phased execution plan:
Days 1-30: Foundation (optimize profiles, establish content cadence, first 4-8 posts)
Days 31-60: Consistency (maintain cadence, engage with others' content, join 1-2 conversations per day)
Days 61-90: Expansion (guest content, collaborations, community participation, reach measurement)
Weekly content calendar with specific posting schedule
Engagement targets (comments, connections, conversations per week)
## Personal Brand Strategy: [User Name or Role]
**Date:** [Date]
**Career goal:** [1-3 year goal]
**Time commitment:** [X] hours per week
---
### Unique Value Proposition
**Positioning statement:** I help [target audience] with [specific problem] by [unique approach].
**Intersection formula:**
- Expertise 1: [Area]
- Expertise 2: [Area]
- Unique perspective: [What makes the user's angle different]
**Proof points:**
1. [Achievement or result that validates expertise]
2. [Achievement or result that validates expertise]
3. [Achievement or result that validates expertise]
### Target Audience
**Primary audience:** [Who] -- [Why their attention matters]
**Secondary audience:** [Who] -- [How they amplify]
**Audience problems the user can address:**
1. [Problem 1]
2. [Problem 2]
3. [Problem 3]
**Where they spend time:** [Platforms and communities]
**Preferred format:** [Content types they engage with]
### Platform Strategy
**Primary platform:** [Platform] -- [Why]
**Secondary platform:** [Platform] -- [Why]
| Platform | Purpose | Content Type | Posting Frequency |
|----------|---------|-------------|-------------------|
| [Platform 1] | [Primary visibility] | [Format] | [X per week] |
| [Platform 2] | [Depth/SEO/community] | [Format] | [X per month] |
### Content Pillars
**Pillar 1: [Theme Name]** -- [Description]
- Topic ideas: [Idea 1], [Idea 2], [Idea 3], [Idea 4], [Idea 5]
- Best format: [Post type]
**Pillar 2: [Theme Name]** -- [Description]
- Topic ideas: [Idea 1], [Idea 2], [Idea 3], [Idea 4], [Idea 5]
- Best format: [Post type]
**Pillar 3: [Theme Name]** -- [Description]
- Topic ideas: [Idea 1], [Idea 2], [Idea 3], [Idea 4], [Idea 5]
- Best format: [Post type]
**Content mix target:** 60% educational | 25% perspective | 15% personal
---
### 90-Day Visibility Plan
#### Days 1-30: Foundation
**Goal:** Establish presence and publish first content
| Week | Actions | Deliverables |
|------|---------|-------------|
| Week 1 | [Action 1], [Action 2] | [Output 1], [Output 2] |
| Week 2 | [Action 1], [Action 2] | [Output 1], [Output 2] |
| Week 3 | [Action 1], [Action 2] | [Output 1], [Output 2] |
| Week 4 | [Action 1], [Action 2] | [Output 1], [Output 2] |
**Month 1 targets:** [X] posts published, [X] new connections, profile fully optimized
#### Days 31-60: Consistency
**Goal:** Build cadence and engagement habits
| Week | Actions | Deliverables |
|------|---------|-------------|
| Week 5 | [Action 1], [Action 2] | [Output 1], [Output 2] |
| Week 6 | [Action 1], [Action 2] | [Output 1], [Output 2] |
| Week 7 | [Action 1], [Action 2] | [Output 1], [Output 2] |
| Week 8 | [Action 1], [Action 2] | [Output 1], [Output 2] |
**Month 2 targets:** [X] posts published, [X] meaningful comments on others' content, [X] new connections
#### Days 61-90: Expansion
**Goal:** Extend reach beyond own network
| Week | Actions | Deliverables |
|------|---------|-------------|
| Week 9 | [Action 1], [Action 2] | [Output 1], [Output 2] |
| Week 10 | [Action 1], [Action 2] | [Output 1], [Output 2] |
| Week 11 | [Action 1], [Action 2] | [Output 1], [Output 2] |
| Week 12 | [Action 1], [Action 2] | [Output 1], [Output 2] |
**Month 3 targets:** [X] posts published, [X] guest or collaborative content, [X] inbound connection requests
---
### Success Metrics (90-Day Review)
| Metric | Target | How to Measure |
|--------|--------|---------------|
| Posts published | [X] | Count |
| Engagement rate | [X]% | Likes + comments / impressions |
| New connections | [X] | Network growth |
| Inbound opportunities | [X] | Messages, invitations, referrals |
| Profile views | [X]% increase | Platform analytics |Always produce a complete brand strategy document with UVP, audience, platforms, content pillars, and 90-day plan -- never generic branding advice
The UVP must be specific to the user's intersection of skills and experience -- reject generic statements like "passionate professional who delivers results"
NEVER recommend more than 2 primary platforms -- focus and consistency beat broad but shallow presence
Content pillar topics must be concrete enough that the user can write about them immediately, not abstract themes like "industry trends"
The 90-day plan must have weekly granularity with specific actions, not monthly goals alone
Time commitment must be realistic for the user's stated availability -- do not prescribe a 10-hour-per-week plan for someone who has 2 hours available
NEVER recommend buying followers, engagement pods, or any artificial growth tactics
Include both content creation and engagement activities -- creating without engaging is broadcasting, not brand-building
Engagement targets must be specific (e.g., "comment on 3 posts per day from target audience members") not vague ("engage with the community")
If the user has no existing online presence, add a "Week 0" setup phase to the plan covering profile creation and initial optimization
User has no idea what they want to be known for: Guide them through a discovery exercise: What questions do colleagues come to them for? What topics can they talk about for 30 minutes without preparation? What work are they most proud of? Use answers to draft 2-3 UVP options and let the user choose.
User works in a highly regulated industry (finance, healthcare, law): Add compliance considerations to the content strategy. Note that all content should be reviewed against employer social media policies. Focus on educational and thought-leadership content that shares frameworks and perspectives rather than specific advice or client information.
User wants to build a personal brand while job hunting: Adjust the strategy for dual purpose: attract recruiters and hiring managers while building industry visibility. Front-load content that demonstrates competence and domain knowledge. Add job search signals to the platform strategy (e.g., "Open to Work" on LinkedIn).
User has a negative or controversial online history: Address this directly. Recommend auditing and cleaning up existing profiles before starting new content. The 90-day plan should include reputation recalibration by consistently publishing high-quality content that establishes the desired narrative.
User is a freelancer or consultant seeking clients: Shift the brand strategy from career advancement to client acquisition. Content pillars should address client pain points directly. Include case study and results-oriented content that demonstrates ROI. Add a call-to-action strategy for converting content viewers into leads.
Input: "I'm a data engineer with 6 years of experience. I want to become known as an expert in data pipeline architecture. My goal is to move into a senior or staff engineer role in the next 2 years. I have about 3 hours per week. I have a LinkedIn profile but I've never posted anything."
Output:
Date: [Current date] Career goal: Senior/Staff Data Engineer within 2 years Time commitment: 3 hours per week
Positioning statement: I help data teams build reliable, scalable pipelines by sharing practical architecture patterns from 6 years of building production data systems.
Intersection formula:
Expertise 1: Data pipeline architecture and orchestration
Expertise 2: Production system reliability and failure recovery
Unique perspective: Practical lessons from building and maintaining real systems, not theoretical best practices
Proof points:
6 years of hands-on data engineering across production environments
[Specific pipeline or system built -- scale, complexity, business impact]
[Specific challenge solved -- migration, reliability improvement, cost reduction]
Primary audience: Hiring managers and senior engineers at companies with complex data infrastructure -- their attention opens doors to senior/staff roles Secondary audience: Mid-level data engineers who will engage with and amplify technical content
Audience problems the user can address:
How to design pipelines that do not break at 10x scale
How to choose between orchestration tools for different use cases
How to debug and recover from pipeline failures without data loss
Where they spend time: LinkedIn, data engineering communities, technical blogs Preferred format: Short technical posts (LinkedIn), detailed write-ups (blog)
Primary platform: LinkedIn -- highest concentration of hiring managers and senior engineers in data Secondary platform: Personal blog or newsletter -- long-form technical depth for SEO and portfolio
| Platform | Purpose | Content Type | Posting Frequency |
|---|---|---|---|
| Primary visibility, hiring manager reach | Short technical posts (200-400 words) | 2 per week | |
| Personal blog | Depth, SEO, portfolio | Long-form technical write-ups (800-1500 words) | 1 per month |
Pillar 1: Pipeline Architecture Patterns -- Specific patterns for common data pipeline challenges
Topic ideas: batch vs. streaming decision framework, idempotent pipeline design, schema evolution strategies, backfill architecture, multi-tenant pipeline isolation
Best format: LinkedIn post with diagram or code snippet
Pillar 2: Reliability and Failure Recovery -- How to build pipelines that recover gracefully
Topic ideas: circuit breaker patterns for data pipelines, monitoring and alerting strategies, dead letter queue design, data quality gates, incident post-mortem lessons
Best format: LinkedIn post (short) + blog post (detailed case study)
Pillar 3: Lessons from Production -- Real stories from building and maintaining data systems
Topic ideas: the migration that taught me about testing, scaling from 1M to 100M rows per day, why I stopped using [approach] and switched to [approach], the cost optimization that saved $X per month, debugging a silent data corruption issue
Best format: LinkedIn narrative post (personal story format)
Content mix target: 60% educational | 25% perspective | 15% personal
Optimize LinkedIn profile: headline includes "Data Engineer | Pipeline Architecture," about section states UVP
Professional headshot if not already present
Set up blog platform with first draft post in progress
| Week | Actions | Deliverables |
|---|---|---|
| Week 1 | Write and publish first LinkedIn post (Pillar 1 topic), comment on 3 data engineering posts per day | 1 LinkedIn post published, 15 comments |
| Week 2 | Write and publish second LinkedIn post (Pillar 3 story), connect with 10 data engineers | 1 LinkedIn post, 10 connection requests |
| Week 3 | Publish first blog post (detailed Pillar 1 topic), share on LinkedIn | 1 blog post, 1 LinkedIn share post |
| Week 4 | Write 2 LinkedIn posts (Pillar 1 and Pillar 2), continue daily commenting | 2 LinkedIn posts, 15 comments |
Month 1 targets: 5 LinkedIn posts, 1 blog post, 60 comments on others' content, 20 new connections
| Week | Actions | Deliverables |
|---|---|---|
| Week 5 | 2 LinkedIn posts, start engaging with data engineering community leaders | 2 posts, identify 5 key voices to engage with |
| Week 6 | 2 LinkedIn posts, publish second blog post | 2 LinkedIn posts, 1 blog post |
| Week 7 | 2 LinkedIn posts, respond to every comment on own posts within 24 hours | 2 posts, 100% comment response rate |
| Week 8 | 2 LinkedIn posts, connect with 10 senior engineers or hiring managers | 2 posts, 10 targeted connections |
Month 2 targets: 8 LinkedIn posts, 1 blog post, 60 comments, 20 new targeted connections
| Week | Actions | Deliverables |
|---|---|---|
| Week 9 | 2 LinkedIn posts, pitch a guest post to a data engineering publication or newsletter | 2 posts, 1 pitch sent |
| Week 10 | 2 LinkedIn posts, publish third blog post, share a post that references another creator's work | 2 LinkedIn posts, 1 blog post, 1 collaborative mention |
| Week 11 | 2 LinkedIn posts, participate in a data engineering discussion thread or community event | 2 posts, 1 community contribution |
| Week 12 | 2 LinkedIn posts, 90-day review and strategy adjustment | 2 posts, written review of metrics vs. targets |
Month 3 targets: 8 LinkedIn posts, 1 blog post, 1 guest or collaborative content, measurable inbound interest
| Metric | Target | How to Measure |
|---|---|---|
| Posts published (LinkedIn) | 21 | Count |
| Blog posts published | 3 | Count |
| Engagement rate | 3-5% | Likes + comments per post / impressions |
| New connections | 60 | LinkedIn network growth |
| Inbound messages or opportunities | 3+ | Recruiter messages, collaboration invites, referrals |
| Profile views | 50% increase | LinkedIn analytics comparison month 1 vs. month 3 |
SKILL.md
339 lines · 2,686 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Personal Brand Strategy bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for