write-evidence-backed-profile
Skill3 starsChanged 6 months agoMITView on GitHub
Draft bios, applications, portfolio introductions, proposal introductions, cover notes, and professional profile copy from approved evidence without inventing experience or results. Use when a user wants personal or company positioning tailored to an audience, role, opportunity, directory, portfolio, proposal, or public profile and factual grounding matters.
In this repository47 other files it gives its agents.
- agents-md-writerSkill
- ai-image-run-pacingSkill
- automation-state-reconcilerSkill
- backup-readiness-auditorSkill
- brand-voice-linterSkill
- case-study-writerSkill
- client-delivery-auditorSkill
- client-intake-builderSkill
- client-workspace-scaffolderSkill
- code-deduplicatorSkill
- cold-outreach-writerSkill
- demo-animationSkill
- demo-animation-v2Skill
- discovery-briefSkill
- em-dash-removerSkill
- etsy-listing-optimizerSkill
- follow-up-radarSkill
- github-profile-proof-updaterSkill
- github-safe-publisherSkill
- idea-inboxSkill
- implement-client-feedbackSkill
- lead-scorerSkill
- llms-txt-generatorSkill
- local-app-public-demoSkill
- media-spec-checkerSkill
- obsidian-daily-noteSkill
- ops-status-reportSkill
- outreach-pipeline-designerSkill
- php-form-mailerSkill
- proposal-writerSkill
- release-announcement-writerSkill
- remove-ai-image-metadataSkill
- research-brief-curatorSkill
- research-to-articleSkill
- screen-recorderSkill
- session-handoffSkill
- skill-builderSkill
- skill-reviewerSkill
- social-campaign-proof-trackerSkill
- skill-nameSkill
- thumbnail-legibility-checkSkill
- thumbnail-set-designerSkill
- vault-janitorSkill
- verify-public-claimsSkill
- web-scraperSkill
- website-change-verifierSkill
- windows-reinstall-plannerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 13 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
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
- Distinctive: line 8
Create audience-specific profile writing from an approved evidence set.
- Distinctive: line 14
Read references/channel-output-rules.md for the selected format.
- Distinctive: line 19
Use assets/evidence-pack-template.md when the user has not supplied a structured source set.
- Distinctive: line 20
Use public sources and user-approved facts only.
- Distinctive: line 21
Verify current pages when roles, availability, metrics, projects, credentials, services, or positioning may have changed.
- Distinctive: line 22
Treat inaccessible sources and unsupported user expectations as unverified.
- Distinctive: line 23
Do not embed a specific person's identity, CV, website, source registry, or voice guide in the skill.
- Distinctive: line 34
Do not infer job titles, customer relationships, years of experience, technical depth, revenue, performance, availability, awards, or …
- Distinctive: line 40
Use concrete public work when it improves credibility.
- Distinctive: line 42
Avoid inflated certainty, unsupported superlatives, fabricated enthusiasm, and irrelevant capability lists.
- Distinctive: line 47
Verify every name, title, date, link, metric, project description, and factual statement used.
- Distinctive: line 49
Keep sensitive or user-approved non-public material out of reusable examples and public artifacts.
- Distinctive: line 50
Never submit a form, send a message, edit a public profile, or publish the draft.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Write Evidence-Backed Profile
Create audience-specific profile writing from an approved evidence set. Prefer a smaller defensible story over a broad invented persona.
1. Define the writing task
- Confirm the audience, channel, prompt or field, word or character limit, desired action, and tone.
- Identify the claims the user expects the draft to communicate.
- Read references/channel-output-rules.md for the selected format.
- Preserve exact names, links, titles, dates, and wording supplied for the current task.
2. Build or inspect the evidence pack
- Use assets/evidence-pack-template.md when the user has not supplied a structured source set.
- Use public sources and user-approved facts only.
- Verify current pages when roles, availability, metrics, projects, credentials, services, or positioning may have changed.
- Treat inaccessible sources and unsupported user expectations as unverified.
- Do not embed a specific person's identity, CV, website, source registry, or voice guide in the skill.
3. Map evidence to the audience
For each important requested claim, record:
- the evidence that supports it
- whether it is direct experience, adjacent experience, interpretation, or unsupported
- why it matters to this audience
- the strongest wording the evidence permits
Do not infer job titles, customer relationships, years of experience, technical depth, revenue, performance, availability, awards, or credentials from weak signals.
4. Write the strongest honest version
- Lead with the most relevant supported overlap between the evidence and the audience's need.
- Present adjacent experience as adjacent, not direct expertise.
- Use concrete public work when it improves credibility.
- Omit unsupported claims instead of filling gaps with generic confidence.
- Avoid inflated certainty, unsupported superlatives, fabricated enthusiasm, and irrelevant capability lists.
- Match the requested format so the result is ready for human review and use.
5. Complete the evidence check
- Verify every name, title, date, link, metric, project description, and factual statement used.
- List requested claims that were qualified or omitted and explain the evidence gap briefly.
- Keep sensitive or user-approved non-public material out of reusable examples and public artifacts.
- Never submit a form, send a message, edit a public profile, or publish the draft.
Return the compact evidence map, finished draft, qualifications, omitted claims, sources checked, and any fact that still needs confirmation.
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
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.

