git:20260912.6ee419c to git:20260928.53ba292

16 added, 1 removed. Audit A to A.

---

name: person-profile-writing

description: Research, draft, or revise source-grounded biographies and person-centered speaker, founder, or expert profiles. Use when identity resolution, career chronology, roles, projects, public ideas, or attribution are central to the deliverable. Pair with research-grounded-writing for evidence and swyx-writing for prose.

---

# Person profile writing

Produce an accurate account of a person and why their work matters. Apply

`research-grounded-writing` to the evidence and `swyx-writing` to the prose.

This skill owns the identity and biography-specific decisions.

## Establish who the subject is

Build an evidence packet when important facts remain uncertain:

- Start with the person's own site and verified profiles, official employer or

founder pages, company announcements, owned repositories, authored work,

recorded talks, and available transcripts.

- Use substantive posts from independently verified accounts when they clarify

priorities, arguments, technical work, or voice. Distinguish original posts

from reposts, advertisements, engagement, and other people's claims.

- Corroborate identity through full name plus organization, verified account,

owned project, event identity, or another independent signal. Never merge

people because their names resemble each other.

- Reconstruct only a defensible chronology: current roles when independently

established, founding history, significant contributions, recurring ideas,

and meaningful changes over time.

- Treat event affiliations as historical unless another source establishes a

current position. Do not infer education, employment dates, ownership,

quantitative accomplishments, private circumstances, or another person's

opinions.

Use `smart-entity-resolution` only when the identity is genuinely ambiguous.

## Write the person

Lead with the strongest supported identity and contribution. The opening should

explain who this particular person is and why their work matters. A conference,

profile page, article, or citation should not become the main character.

Weave career transitions, projects, technical ideas, public writing, talks, and

distinctive posts into a coherent account. Use transcripts for concrete insight

instead of producing a sequence of presentation summaries. Preserve the

distinctions between participation, authorship, ownership, employment, and

claims about third-party products.

Choose chronology or another structure according to what best explains the

person. Source-poor profiles should remain brief. Extensive evidence justifies

more development only when it adds understanding.

## Evaluate profile batches

For a generation pipeline, calibrate on a sample spanning evidence-rich and

evidence-poor subjects, disputed identities, varied careers, different source

types, and formatting edge cases.

+ Evaluate usefulness without requiring a site-specific reference: the opening

+ identifies this particular person, supported contributions are explained concretely,

+ and the account develops coherently without repetition or generic career padding.

+ Meaningful links and navigation help readers investigate the work. Examples from

+ other corpora illustrate those qualities, not a required style, length or outline.

+ When approved examples are supplied, compare complete profiles rather than their

+ headings or length. Assess factual support and editorial usefulness separately:

+ does the draft explain this person’s distinctive contributions and development,

+ or merely recount the latest talk? Select useful mechanisms and examples without

+ turning refinement into a transcript walkthrough. Source-poor brevity is valid;

+ missing optional career details are not a reason to invent or demand a dossier.

+ Repair substantive repetition, confusing selection or lost contributions locally;

+ preferences about length or outline alone are not rejection grounds.

Check identity fidelity, supported chronology, ownership and attribution,

meaningful links, private-source exclusion, and destination rendering. Persist

accepted evidence and revisions so retries do not repeat successful paid work.

- Keep research, synthesis, editorial compression, validation, and publication

+ Keep research, synthesis, editorial development, validation, and publication

separate when those boundaries improve the pipeline.