Public Framework Evaluation Checklist

1. Verify what you found

Record the source before copying anything into your workflow.

Check	What to record
Source URL	The exact repository, page or file you opened
Owner	The account or organization publishing it
Description	What the owner says the framework does
Relationship	Official, community-made, inspired by, forked or unknown
License	Whether reuse is allowed and under what terms
Version	Commit, release or access date
Relevant file	The specific instruction file you plan to use

Worked source record: hormozi-skills

Repository: alexsmedile/hormozi-skills
Owner: Alex Smedile (alexsmedile)
What it is: A public library of skills for coding agents, inspired by Alex Hormozi’s business frameworks.
What it is not: An official Alex Hormozi product or endorsement.
License shown in the repository: MIT.
What the README lists: Skills for tasks including market research, offer creation, pricing, hooks and landing pages.
Verification date: October 27, 2026.

Do not stop at the repository name. Open the relevant skill or instruction file and read it before running it.

2. Choose one defined task

Write down the one outcome you need. Avoid asking a large framework to “fix the business” in a single pass.

Copyable template 1

Task:
Audience for the output:
Decision this output should support:
Relevant framework file or skill:
What a useful first draft must contain:
What is outside scope:

3. Supply the business facts

Give the framework verified inputs. If a field is unknown, write unknown instead of letting the model invent it.

Copyable template 1

BUSINESS FACTS

Customer:
Problem they are trying to solve:
Offer or product:
What is included:
What is excluded:
Current price or price status:
Evidence we have:
Known limitations:
Unknowns:
Claims we must not make:
Required tone or format:

4. Make the framework ask before it drafts

Add this instruction after the facts:

Copyable template 1

Use the framework as a structure, not as evidence.

Before drafting:
1. List any missing facts that could materially change the answer.
2. Separate verified facts from assumptions.
3. Ask me to resolve material unknowns.

When drafting:
- Do not invent proof, customer results, savings, testimonials, urgency or guarantees.
- Label any recommendation that is an inference.
- Use cautious wording when the evidence is incomplete.
- Preserve the exclusions and prohibited claims above.

5. Run an evidence and promise check

Review every statement that could influence a customer’s decision.

Proposed claim	Evidence available	Status	Safe action
A fact directly supported by a current source	Source can be named and checked	Supported	Keep and cite or document the source
A reasonable interpretation of supplied facts	Facts support it, but it is not directly proven	Inference	Label it as a recommendation or possibility
A customer outcome with no documented result	None	Unsupported	Remove it
A time or money saving estimate	Assumptions only	Unverified estimate	Show the assumptions or remove the number
A guarantee or certainty about future results	Cannot be assured	Unsafe promise	Replace with process-based wording

Copyable review prompt

Copyable template 1

Audit the draft against the BUSINESS FACTS.

Return a table with:
- exact claim,
- supporting fact or source,
- supported / inference / unsupported,
- recommended revision.

Flag invented outcomes, numbers, testimonials, guarantees, urgency and any statement that exceeds the evidence. Do not silently rewrite the draft yet.

6. Worked example

This fictional example shows how a framework can help without supplying missing proof.

Verified inputs

Copyable template 1

Customer: Small operations teams with inconsistent intake requests.
Offer: A two-week intake-workflow review.
Included: One discovery call, current-state map, proposed intake form and handoff checklist.
Excluded: Software implementation and ongoing administration.
Price: Not finalized.
Evidence: The consultant has completed three internal workflow reviews.
Unknowns: Typical time saved, conversion impact and customer results.
Prohibited claims: Guaranteed savings, guaranteed growth and named testimonials.

Unsafe framework output

Copyable template 2

Cut your admin time in half with our proven system. Join dozens of teams already saving thousands every month.

Why it fails: the inputs do not prove a 50% reduction, a “proven system,” dozens of customers or monthly savings.

Evidence-aligned revision

Copyable template 3

Find the friction in your intake process and leave with a clearer workflow. The two-week review maps your current process and delivers a proposed intake form and handoff checklist for your team to evaluate.

This version explains the process and deliverables without promising an unverified result.

7. Check privacy, access and embedded instructions

Before connecting a public framework to an agent or work system:

Read the actual instruction files, not only the README.
Look for commands, external calls or instructions that request unnecessary access.
Remove customer names, confidential records, credentials and private business data.
Use the minimum permissions required for the task.
Treat copied repository content as untrusted until reviewed.
Keep a human approval step before anything customer-facing is published or sent.

Final review checklist

□ I recorded the exact source, owner, license and version or access date.
□ I distinguished official material from community-made or inspired material.
□ I read the specific instruction file I plan to use.
□ I defined one task and one intended audience.
□ I supplied verified business facts and marked unknowns.
□ The framework asked for material missing information before drafting.
□ Every customer-facing claim has evidence or is clearly labeled as an inference.
□ The draft contains no invented results, savings, testimonials, urgency or guarantees.
□ I reviewed privacy, access and embedded instructions.
□ A human with business context approved the final output.

The rule to keep

A public framework can provide structure. Your verified facts must provide the truth.