agentleFS
Sign inStart free
harshsinghmpharshsinghmp/muse-skills/skills/agency-delivery/brand/SKILL.md

brand

Skill1 starsChanged 17 days agoMITView on GitHub

Client and brand lifecycle engine: comprehensive brand intake, autonomous web research, sales pipeline qualification, ad and payment account access, cross-department brief synthesis, cross-border e-commerce operations, offboarding, brand asset fencing/font auditing, and multimodal story engine genesis — routed through eleven modes. Use when onboarding a new client or brand, scraping brand assets and web signals, qualifying sales leads, gathering ad account and payment credentials, synthesizing cross-department briefs, scaling cross-border e-commerce, generating brand narrative archetypes and OKLCH story matrices, auditing brand asset fencing and font licenses, offboarding an account, or auditing brand readiness checklists. Not for designing brand marks (design) or negotiating contracts (ops).

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every invocation resolves to exactly one mode.

    line 38
  2. Distinctive:

    Only the resolved mode's reference is loaded — the rest stay on disk, saving tokens on every run.

    line 53
  3. Very specific:

    Brand Readiness Gate (audit): Run the 50-checkpoint Brand Readiness Audit.

    line 98
  4. Distinctive:

    Accepting Raw Passwords / Secrets: Never ask clients to paste passwords or API keys into chat or docs.

    line 105
  5. Distinctive:

    Assumed Brand Truth: Don't rely solely on what the client says.

    line 106
  6. Very specific:

    Unclear Downstream Handoffs: Avoid handing raw, rambling call notes to design or webdev.

    line 107

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

🏷️ brand — Client & Brand Lifecycle Department

One unified department for client and brand lifecycle management. Every agency engagement begins and ends here. It drives end-to-end sales pipeline progression, conducts comprehensive brand discovery and autonomous web intelligence, audits ad account and payment access, translates raw brand truth into tailored cross-department briefs (design, webdev, content, paidads, qa-launch), audits brand readiness with interactive clarification questions, and governs graceful offboarding.

Modes

Every invocation resolves to exactly one mode. Match the request, then load only the matched reference:

ModeTrigger phrasesBehaviorReference
intake"onboard client", "brand intake", "client questionnaire", "brand discovery"Comprehensive brand intake discovery with automatic missing-field question promptsreferences/intake.md
research"scrape brand", "brand research", "competitor intelligence", "web audit"Autonomous web scraping, social footprint harvesting, and competitive positioningreferences/research.md
pipeline"sales pipeline", "qualify lead", "BANT qualification", "sales discovery"Full agency sales pipeline: Lead Gen → Discovery/Qualification → Proposal → SOW Handoverreferences/pipeline.md
accounts-access"account access", "client creds", "login credentials", "ad account setup", "payment credentials", "2fa setup"5-stage client credentials and logins intake workflow: discovery, zero-leak delegation dispatch, 2FA handshake, permission audit, and vault loggingreferences/accounts-access.md
brief"brand brief", "client brief", "cross-department brief", "brand dossier"Synthesizes master Single Source of Truth Brand Dossier for downstream delivery headsreferences/brief.md
ecommerce"cross-border ecommerce", "amazon listing", "shopee store", "tiktok shop", "global ecommerce", "international logistics", "fba", "vat compliance"Multi-platform cross-border e-commerce operations: Amazon, Shopee, Lazada, Temu, TikTok Shop, international logistics/warehousing, VAT/EPR compliance, multilingual listing optimization, and unit economics modelingreferences/ecommerce.md
offboard"offboard client", "client offboarding", "revoke access", "project handover"Access revocation, asset export packaging, DNS handover, and client NPS reviewsreferences/offboard.md
assets"brand assets", "font licensing", "vector logo check", "brand asset fencing", "color contrast certification", "asset audit"Brand asset fencing, font license isolation, SVG sanitization, and OKLCH color contrast certificationreferences/assets.md
story-engine"brand genesis", "story engine", "founder story", "brand narrative", "brand archetype", "voice constitution"Multimodal brand narrative genesis, founder archetype synthesis, OKLCH visual color resonance, tagline matrix, and voice constitutionreferences/story-engine.md
audit"brand audit", "readiness check", "intake checklist", "missing brand info"Pre-flight brand readiness gate auditing completeness before teams begin workreferences/audit.md

Only the resolved mode's reference is loaded — the rest stay on disk, saving tokens on every run.

Support references (load on topic)

Loadable by topic; also routable as /brand-<file> commands (not separate routed modes):

  • persona.md

When to Use

  • Onboarding a new agency client or launching a new internal or external brand.
  • Conducting web scraping, social research, and competitive intelligence on a brand.
  • Qualifying inbound and outbound sales leads using BANT / MEDDIC frameworks.
  • Collecting and auditing ad account permissions (Meta, Google, TikTok), analytics (GA4, GTM), hosting, and payment gateways under strict zero-leak protocols.
  • Generating tailored cross-department briefs for design, webdev, content, paidads, and qa-launch.
  • Auditing brand readiness and automatically asking clarifying questions when critical details are missing.
  • Auditing incoming brand assets, isolating font licenses, and certifying OKLCH color contrast.
  • Executing a clean, professional client offboarding and asset handover.

Quick Reference

ModePrimary InputPrimary OutputGate / SLA
intakeClient questionnaire or discovery call notesStructured Brand Intake Document (brand-intake.md)Zero unverified core claims
researchBrand URL, social handles, competitor namesWeb Intelligence & Market Dossier (brand-intelligence.md)Primary sources cited
pipelineLead profile, initial budget, timelineQualified Opportunity Record & Proposal BlueprintBANT / MEDDIC scored
accounts-accessPlatform asset IDs, delegation requestsVerified Access Inventory & Delegation TableZero raw secrets exposed
briefCompleted intake & research dataTailored Departmental Briefs (.agents/context/brand.md)100% downstream parity
offboardFinished project SOW, termination noticeOffboarding Certificate & Revocation Log48h access revoking
auditBrand dossier drafts & asset linksReadiness Scorecard (Block / Ready to Build)$\ge 90%$ completeness

Procedure

  1. Pipeline & Qualification (pipeline): Receive lead, assess ICP fit, run BANT/MEDDIC qualification, and draft initial scope proposal before contracts.
  2. Deep Brand Intake (intake): Conduct comprehensive intake across business model, target audience, brand pillars, core offers, and visual preferences. Detect missing fields and trigger interactive clarification questions.
  3. Autonomous Web Scraping & Research (research): Scrape public website, social profiles, customer reviews (G2/Trustpilot), meta tags, schema markup, and competitor positioning.
  4. Access & Delegation Vault (accounts-access): Send platform-native delegation guides (Partner Access on Meta Business Manager, Manager Account on Google Ads, Organization access on Stripe/GA4). Never accept raw passwords.
  5. Master Brief Synthesis (brief): Compile the canonical Brand Dossier (.agents/context/brand.md) and carve out specific departmental sub-briefs for design, webdev, content, paidads, and qa-launch.
  6. Brand Readiness Gate (audit): Run the 50-checkpoint Brand Readiness Audit. If any critical parameter is missing, generate targeted clarification questions and block unverified downstream execution.
  7. Clean Offboarding (offboard): Upon project completion, execute the access revocation protocol, export all production assets, deliver documentation, and request a structured review.

Pitfalls

  • Accepting Raw Passwords / Secrets: Never ask clients to paste passwords or API keys into chat or docs. Always use native delegation (Meta Business Manager Partner IDs, Google Ads Manager link, GTM User Invitations).
  • Assumed Brand Truth: Don't rely solely on what the client says; scrape the actual live website and customer reviews to identify perception gaps.
  • Unclear Downstream Handoffs: Avoid handing raw, rambling call notes to design or webdev. Always synthesize into the structured Department Brief schema.
  • Skipping the Readiness Gate: Starting design or development with incomplete brand assets leads to costly rework and scope creep. Halt until the audit passes $\ge 90%$.

Verification

  • All 7 mode reference files exist and are syntactically valid in references/.
  • Frontmatter conforms to Hermes, OpenClaw, and RFC specifications.
  • Automated intake audit script (scripts/intake-audit.ts) executes and scores brand completeness.
  • Vibeguard zero-credential leak protocol strictly maintained across all account-access guides.

Download now (ZIP)

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.

Check your setup, free