Skip to content
Back to skills

Write Evidence Backed Profile

ASecurity

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.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 15, 2026
ai-agentsperformance

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned October 15, 2026

npx -y skills add jqaisystems/jqai-ai-skills --skill write-evidence-backed-profile --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Write Evidence Backed Profile?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Write Evidence Backed Profile
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jqaisystems-write-evidence-backed-profile/badge)](https://www.skillsdirectory.com/skills/jqaisystems-write-evidence-backed-profile)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: write-evidence-backed-profile
description: 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.
---

# 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](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](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.

Files in this skill

  • SKILL.md3 KB
  • agents/openai.yaml239 B
  • assets/evidence-pack-template.md1.1 KB
  • references/channel-output-rules.md1.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.