agentleFS
getedgehqgetedgehq/skills/albro-founder-brand/SKILL.md

albro-founder-brand

Skill5 starsChanged 13 days agoApache-2.0View on GitHub

Build a buyer-focused founder narrative, content plan, distribution routine, and revenue hook using Scott Albro's public method when a startup founder needs a credible brand that creates qualified sales conversations.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Frame the assignment: Read the method's scope and evidence rules.

    line 20
  2. Distinctive:

    Collect the founder's raw material: Follow evidence and voice guidance.

    line 24
  3. Distinctive:

    Build all three story columns: Use the story architecture and the corresponding template fields.

    line 26
  4. Distinctive:

    Establish an authentic voice: Use evidence and voice guidance to name the founder's natural style and recognizable behaviors.

    line 30
  5. Distinctive:

    Create a usable content batch: Follow content production rules.

    line 32
  6. Distinctive:

    Choose distribution and participation: Use channel selection rules.

    line 36
  7. Distinctive:

    Design the revenue hook: Follow engagement and follow-up rules.

    line 38
  8. Distinctive:

    Review and iterate: Run the pass/fail checklist, repair failures, and mark unresolved assumptions.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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

Founder Brand Workshop

Based on Scott Albro's public method. Not affiliated with or endorsed by Scott Albro.

When to use

Use this skill when a startup founder needs to explain why the company exists, articulate a distinctive market view, decide what to publish, choose where to participate, or turn relevant engagement into sales conversations. It also supports reviewing an existing founder narrative or content plan for buyer relevance and commercial usefulness. The intended deliverable is a founder brand working plan with publishable draft content and a proposed follow-up path. [S1][S3][S6]

Albro's framework connects four pillars: story, content, distribution, and monetization, all grounded in a known target market. Begin with the buyer rather than a personal popularity goal. If the buyer is uncertain, make that uncertainty visible and produce a provisional discovery brief before presenting the strategy as ready. This skill supports founder branding, not a complete company brand redesign or general influencer growth program. [S2][S3]

Use only the detail needed for the request. A post revision may need the story and voice rules; a full strategy needs every pillar. Keep the founder's actual knowledge and language central. The agent may organize, challenge, and edit that material, but should not fabricate experiences or replace the founder's voice with a creator persona. Deliver drafts and proposed actions within the user's scope; publishing and outreach require their own authorization.

Procedure

  1. Frame the assignment. Read the method's scope and evidence rules. Identify the requested artifact, target buyer, buying context, and desired commercial action. State missing information as questions or provisional assumptions. Use the output template to establish what the final plan must contain.
  2. Define the perception to change. Apply buyer and perception rules. Write what buyers currently believe, what the founder wants them to believe, and why that change should help a meeting or purchase decision. Avoid reputation goals that cannot be connected to buyer behavior. [S2][S3]
  3. Collect the founder's raw material. Follow evidence and voice guidance. Gather conversations, decisions, observations, relevant personal history, and shareable outcomes. Separate verified facts, founder interpretations, forecasts, and unknowns. Resolve confidential material before placing it in publishable copy.
  4. Build all three story columns. Use the story architecture and the corresponding template fields. Develop customer priority, market transformation, and personal journey stories, including themes, evidence, and a distinctive point of view. Allow meaningful overlap among columns. [S2][S5]
  5. Challenge differentiation and scale. Apply the differentiation test. Ask what this founder can credibly say that competitors cannot. Connect practical advice to a larger market belief when warranted. Keep disagreement grounded in evidence rather than manufactured controversy. [S2][S3]
  6. Establish an authentic voice. Use evidence and voice guidance to name the founder's natural style and recognizable behaviors. Draft a core narrative and a short spoken version. Read both aloud and replace borrowed creator language with the founder's own vocabulary. [S3][S5]
  7. Create a usable content batch. Follow content production rules. Generate two or three ideas per story type for a full plan, with an observation, buyer takeaway, format, and opening. Produce the requested drafts. Consult worked examples for how weak claims become useful, specific content. [S5]
  8. Set format and cadence. Apply cadence decisions. Choose writing, speaking, or video based on founder comfort and buyer context. Set initial dates, capacity, and a recovery plan. Preserve Albro's three-times-weekly recommendation while explicitly noting any capacity adaptation. [S2][S3][S5]
  9. Choose distribution and participation. Use channel selection rules. Compare buyer presence, format support, and publishing effort. Select one primary channel and a routine for substantive comments and relevant replies, then record both in the template. [S2][S3]
  10. Design the revenue hook. Follow engagement and follow-up rules. Map each signal to buyer fit, founder first touch, qualification, and a meeting invitation. Draft a short personal note without assuming a like or impression establishes buying intent. [S2][S3]
  11. Review and iterate. Run the pass/fail checklist, repair failures, and mark unresolved assumptions. Specify how qualified conversations and buyer feedback will inform the next batch. Return the requested artifact with evidence limitations and the next review point, without promising conversion results.

Files in this skill

  • SKILL.md: Entry point, use conditions, and the agent's main loop.
  • references/method.md: Detailed principles, decision rules, warnings, and edge cases.
  • references/sources.md: Fetched public sources and their contributions, indexed by [S#].
  • examples/worked-examples.md: Invented before-and-after illustrations with rule explanations.
  • templates/output-template.md: Fill-in founder brand plan with field guidance.
  • checklists/review-checklist.md: Pass/fail review and common failures with fixes.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.