business-profile-creator
Skill4 starsChanged 11 days agoMITView on GitHub
Update a business context profile by read-and-merge. For this operation it reads knowledge/business/operator-business-profile.json and knowledge/memory.md BEFORE asking anything, diffs field by field, and never blank-slate overwrites. Profiles for any other business write to outputs/, never knowledge/.
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create a structured business profile that captures your company's identity, offerings, positioning, and brand voice for use in AI-assisted …
- Distinctive: line 18
Diff, never replace: Every field the operator does not change carries over byte for byte, including fields the question list below never …
- Distinctive: line 51
Ask these questions one at a time, waiting for responses:
- Distinctive: line 94
After gathering responses, generate a JSON file following this structure:
- Distinctive: line 151
Ask questions conversationally, one at a time
- Distinctive: line 153
If answers are vague, ask clarifying follow-ups
- Distinctive: line 155
After all questions, generate the complete JSON
- Distinctive: line 163
Keep the tone professional but friendly
- Very specific: line 166
Check that the profile captures the unique positioning.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Business Profile Creator
Create a structured business profile that captures your company's identity, offerings, positioning, and brand voice for use in AI-assisted content creation.
Hard rules (this repo)
This started as a generic third-party interview template. It is repaired, not generic. These five rules override every step below, including the interview script.
- Read before you ask. Load
knowledge/business/operator-business-profile.jsonandknowledge/memory.mdin full BEFORE the first question. The existing profile is the baseline. The interview fills gaps and applies changes the operator states, nothing more. - Diff, never replace. Every field the operator does not change carries over byte for byte,
including fields the question list below never asks about. Present a field-level diff (added /
changed / unchanged) and get an explicit yes before writing. A blank-slate rebuild is a defect,
not an option, and it is the specific failure this section exists to stop: a rebuilt profile
silently drops every field the interview does not ask about, and nobody notices until a
downstream draft is missing a positioning line nobody remembers writing
(
knowledge/ops/os-roadmap.mdcarries the ruling). - Prices and positioning are mirrored here, never authored here. Pricing authority is
knowledge/business/outbound-offer.mdfor the outbound offer, plus the client roadmap file inknowledge/clients/<client>/roadmap.mdfor a client engagement. If an interview answer conflicts with the pricing authority, stop and flag it. Never write the conflict into the profile. - Two output paths. This operation's own profile writes to
knowledge/business/operator-business-profile.json, which is a sanctionedknowledge/write and needs the operator's explicit ask. A profile for any other business (client onboarding, a new brand) writes tooutputs/profiles/<slug>-profile.jsonand never touchesknowledge/. - Independent check before save. Spawn the
fact-checksubagent with fresh context, passing only the draft JSON path. It re-derives every number, price, entity and date from canonical files. Fix failures and re-run untilVERDICT: PASS. This skill does not validate its own output, which is what it used to do.
When to Use This Skill
- Setting up a new writing system
- Onboarding a new client
- Updating business information after pivots or changes
- Creating context for a new brand or product line
Interview Process
Phase 1: Company Overview
Ask these questions one at a time, waiting for responses:
- "What is your company/brand name?"
- "In one sentence, what do you do?" (This becomes the tagline)
- "Why does your company exist? What's the deeper purpose?" (Mission)
- "Where is your company heading in the next 3-5 years?" (Vision)
Phase 2: Value Proposition
- "What's the #1 result or transformation you help people achieve?"
- "How do you uniquely deliver this result? What's your method or approach?"
- "What are 3 things that set you apart from alternatives?"
Phase 3: Offerings
- "List your paid products/services with brief descriptions and price points"
- "What free resources do you offer (newsletter, lead magnets, community, etc.)?"
Phase 4: Positioning
- "How would you describe your market position (premium, accessible, etc.)?"
- "What category do you compete in?"
- "What's your specific niche or area of focus?"
Phase 5: Brand Voice
- "How would you describe your brand's personality in 3-5 words?"
- "What's the overall tone of your communication?"
- "What values do you want to demonstrate through your content?"
Phase 6: Social Proof & Platforms
- "What are your key metrics or achievements? (subscribers, clients, revenue, features)"
- "What do clients commonly say about working with you?"
- "What platforms are you active on? Include handles/URLs."
Phase 7: Content Strategy
- "What are your 3 main content topics or pillars?"
- "What's your primary call-to-action for content?"
Output Format
After gathering responses, generate a JSON file following this structure:
{
"business_profile": {
"version": "1.0",
"last_updated": "YYYY-MM-DD",
"company_overview": {
"name": "",
"tagline": "",
"mission": "",
"vision": ""
},
"value_proposition": {
"primary_value": "",
"unique_mechanism": "",
"key_differentiators": []
},
"offerings": {
"products": [],
"services": [],
"free_resources": []
},
"positioning": {
"market_position": "",
"competitor_comparison": "",
"category": "",
"niche_focus": ""
},
"brand_voice_summary": {
"personality": "",
"tone": "",
"values_demonstrated": []
},
"social_proof": {
"key_metrics": [],
"testimonial_themes": [],
"notable_clients_or_features": []
},
"content_pillars": {
"primary_topics": [],
"content_mission": "",
"content_style": ""
},
"calls_to_action": {
"primary_cta": {},
"secondary_ctas": []
},
"platforms": {}
}
}Instructions
- Begin with: "I'll help you create your business profile. This will take about 10-15 minutes. I'll ask questions one at a time - just answer naturally."
- Ask questions conversationally, one at a time
- If answers are vague, ask clarifying follow-ups
- After all questions, generate the complete JSON
- Save per hard rule 4: this operation's own profile goes to
knowledge/business/operator-business-profile.json(canonical, sanctioned write, explicit ask only); any other business goes tooutputs/profiles/<slug>-profile.json. Run hard rule 5'sfact-checkpass BEFORE saving, not after. - Provide a summary of the key elements captured
Best Practices
- Keep the tone professional but friendly
- Help users articulate ideas they may struggle to express
- Suggest improvements or clarifications when answers are unclear
- Check that the profile captures the unique positioning. Validation itself is hard rule 5's fresh-context
fact-checkpass, never a self-review by this skill.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- az9713/ai-co-writing-claude-skills★ 6189% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository92 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- analytics-trackingSkill
- app-store-screenshotsSkill
- business-profile-creatorSkill
- call-debriefSkill
- copy-editingSkill
- copywritingSkill
- daily-logSkill
- decision-gauntletSkill
- deep-researchSkill
- hard-taskSkill
- harvestSkill
- invoice-creatorSkill
- landing-pageSkill
- make-interfaces-feel-betterSkill
- ogilvySkill
- onboardSkill
- operational-enterprise-aiSkill
- page-croSkill
- pricing-pageSkill
- product-proof-saasSkill
- proposal-creatorSkill
- prospect-briefSkill
- research-doctrineSkill
- run-coding-sessionSkill
- schema-markupSkill
- seo-auditSkill
- stop-slopSkill
- tailwind-v4Skill
- visual-style-presetsSkill
- web-design-guidelinesSkill
- analytics-trackingSkill
- app-store-screenshotsSkill
- business-profile-creatorSkill
- call-debriefSkill
- copy-editingSkill
- copywritingSkill
- daily-logSkill
- decision-gauntletSkill
- deep-researchSkill
- hard-taskSkill
- harvestSkill
- invoice-creatorSkill
- landing-pageSkill
- make-interfaces-feel-betterSkill
- ogilvySkill
- onboardSkill
- operational-enterprise-aiSkill
- page-croSkill
- pricing-pageSkill
- product-proof-saasSkill
- proposal-creatorSkill
- prospect-briefSkill
- research-doctrineSkill
- run-coding-sessionSkill
- schema-markupSkill
- seo-auditSkill
- stop-slopSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

