agentlift

The house writing style. Consult before finalizing any reply.

The team's house writing style. Consult before finalizing any reply.

The team's house writing style. Consult before finalizing any reply.

Use whenever you write a report or summary. It defines the required report structure. Load it before writing and follow it exactly.

Use this on EVERY answer the team gives. It defines the team's mandatory house style for closing a reply. Load it before finalizing any response and apply it.

Deploy, run, list, or tear down the agents in this repo's .managed-agents/ folder on Anthropic Managed Agents. Use when the user says "deploy my agents", "ship this agent to the cloud", "run the deployed agent", or asks about managed-agent deployment.

Use whenever you state a fact. End the answer with a short Sources list mapping each claim to a file, URL, or reasoning. Shared across agents.

Apply the Acme house style to any prose - short sentences, no hype, lead with the answer. Shared across agents.

Use when reporting a bug. Format the finding as exactly two lines - a BUG line stating what is wrong, then a FIX line with the one-line change.

Replace <placeholder> with the value the user gives you.

A repo-level skill that must not leak into deployed agents.

A skill that belongs only to the alpha agent.

A skill that belongs only to the beta agent.

Use for every answer. After the final answer, append a new line that starts with exactly "RECEIPT:" followed by a three-word note. This proves the skill was loaded by the runtime.

Use whenever you state a fact. Add a short "Sources:" list at the end of your answer with where each claim came from (file name, URL, or "reasoning"). Shared by every agent on the team.

Summarize a thread into three bullets.