agentleFS
astriaaiastriaai/skills/headshots-from-photos/SKILL.md

headshots-from-photos

Skill2 starsChanged 29 days agoMITView on GitHub

Create professional headshots of the actual person in supplied photos or a saved identity reference. Use for "make professional headshots from my photos", LinkedIn portraits, corporate team headshots, or consistent portraits of the same person across backgrounds. Inventing a new face uses avatar. Respect a named provider; portrait advice and prompt-only requests do not authorize generation.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use astria-api for schemas, reference syntax, HTTPS inputs, workspace scope, model discovery, idempotency, and checking completed results.

    line 12
  2. Very specific:

    Use an explicit saved reference.

    line 17
  3. Very specific:

    Use a requested saved template through get_template / run_template, resolving its actual reference slots before submission.

    line 33
  4. Distinctive:

    Do not borrow avatar's invented age, heritage, facial traits, or casting prompt.

    line 43
  5. Distinctive:

    When inspection is available, check resemblance, natural facial proportions, and framing.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Headshots from photos

Produce the requested professional portraits of the supplied person with Astria. Preserve identity and natural features while changing the requested wardrobe, background, lighting, or framing. Do not replace them with an invented face.

Use astria-api for schemas, reference syntax, HTTPS inputs, workspace scope, model discovery, idempotency, and checking completed results.

Establish the identity reference

Use an explicit saved reference; resolve a named identity with list_references and inspect it using get_reference. Otherwise create one identity reference with create_reference from the supplied usable HTTPS photo URLs, using a subject class appropriate to the supplied brief. Use the returned ID and class name on every portrait. Do not create a new reference for each background.

For an attachment or local file, use a real host upload capability or the optional authenticated CLI. If neither can supply accessible URLs, ask for usable media instead of inventing a URL. If no identity input exists, ask for photos or a saved reference rather than generating a stranger.

For a team, keep each person's photos and reference ID separate; a group of faces is not one identity. Preserve the requested headcount and shot count.

Generate the portraits

Use a requested saved template through get_template / run_template, resolving its actual reference slots before submission. Otherwise call list_models and use the selected model or catalog default with generate_images.

Include the returned identity token and class in the text, then describe the requested professional style. For an unspecified style, choose simple studio lighting, a neutral background, natural expression, and professional clothing. Make one image unless the user asks for a set. Use separate prompts for distinct backgrounds or outfits, reusing the identity reference throughout.

Do not borrow avatar's invented age, heritage, facial traits, or casting prompt. Do not infer protected attributes from the identity photos.

Deliver

Retain returned prompt IDs and check get_prompt for each requested output. Present completed images and report pending or failed portraits accurately. When inspection is available, check resemblance, natural facial proportions, and framing. Report an identity mismatch without claiming an exact likeness or automatically spending credits on additional attempts.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.