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.
1---2name: write-evidence-backed-profile3description: 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.4---56# Write Evidence-Backed Profile78Create audience-specific profile writing from an approved evidence set. Prefer a smaller defensible story over a broad invented persona.910## 1. Define the writing task1112- Confirm the audience, channel, prompt or field, word or character limit, desired action, and tone.13- Identify the claims the user expects the draft to communicate.14- Read [references/channel-output-rules.md](references/channel-output-rules.md) for the selected format.15- Preserve exact names, links, titles, dates, and wording supplied for the current task.1617## 2. Build or inspect the evidence pack1819- Use [assets/evidence-pack-template.md](assets/evidence-pack-template.md) when the user has not supplied a structured source set.20- Use public sources and user-approved facts only.21- Verify current pages when roles, availability, metrics, projects, credentials, services, or positioning may have changed.22- Treat inaccessible sources and unsupported user expectations as unverified.23- Do not embed a specific person's identity, CV, website, source registry, or voice guide in the skill.2425## 3. Map evidence to the audience2627For each important requested claim, record:2829- the evidence that supports it30- whether it is direct experience, adjacent experience, interpretation, or unsupported31- why it matters to this audience32- the strongest wording the evidence permits3334Do not infer job titles, customer relationships, years of experience, technical depth, revenue, performance, availability, awards, or credentials from weak signals.3536## 4. Write the strongest honest version3738- Lead with the most relevant supported overlap between the evidence and the audience's need.39- Present adjacent experience as adjacent, not direct expertise.40- Use concrete public work when it improves credibility.41- Omit unsupported claims instead of filling gaps with generic confidence.42- Avoid inflated certainty, unsupported superlatives, fabricated enthusiasm, and irrelevant capability lists.43- Match the requested format so the result is ready for human review and use.4445## 5. Complete the evidence check4647- Verify every name, title, date, link, metric, project description, and factual statement used.48- List requested claims that were qualified or omitted and explain the evidence gap briefly.49- Keep sensitive or user-approved non-public material out of reusable examples and public artifacts.50- Never submit a form, send a message, edit a public profile, or publish the draft.5152Return the compact evidence map, finished draft, qualifications, omitted claims, sources checked, and any fact that still needs confirmation.
jqaisystems