asgeirtj/system_prompts_leaks
Read or triage email, clean up an inbox, draft or send messages, and check delivery.
General styling and tone guidelines for composing HTML emails.
Custom licenceAuto-check passed
Install Composing Emails
$ npx skills add friday-platform/friday-studio --skill composing-emails -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install friday-platform/friday-studio composing-emails --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/system/skills/composing-emails .claude/skills/composing-emails && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "composing-emails" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/composing-emails into .claude/skills/composing-emails/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composing-emails", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/composing-emailsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add friday-platform/friday-studio --skill composing-emails -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install friday-platform/friday-studio composing-emails --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/system/skills/composing-emails .agents/skills/composing-emails && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "composing-emails" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/composing-emails into .agents/skills/composing-emails/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composing-emails", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add friday-platform/friday-studio --skill composing-emails -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install friday-platform/friday-studio composing-emails --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/system/skills/composing-emails .cursor/skills/composing-emails && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "composing-emails" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/composing-emails into .cursor/skills/composing-emails/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composing-emails", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/friday-platform/friday-studio.git --path packages/system/skills/composing-emails--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add friday-platform/friday-studio --skill composing-emails -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install friday-platform/friday-studio composing-emails --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/system/skills/composing-emails .gemini/skills/composing-emails && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "composing-emails" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/composing-emails into .gemini/skills/composing-emails/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composing-emails", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install friday-platform/friday-studio composing-emailsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add friday-platform/friday-studio --skill composing-emails -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/system/skills/composing-emails .github/skills/composing-emails && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "composing-emails" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/composing-emails into .github/skills/composing-emails/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composing-emails", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add friday-platform/friday-studio --skill composing-emails -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install friday-platform/friday-studio composing-emails --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/system/skills/composing-emails .opencode/skills/composing-emails && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "composing-emails" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/composing-emails into .opencode/skills/composing-emails/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composing-emails", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
composing-emails- GitHub stars
- 104
- Token cost
- ~648 tokens
- SKILL.md length
- 280 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
General styling and tone guidelines for composing HTML emails.
- Works in 3 steps: Signal schema declares the recipient as… → Action prompt interpolates from the… → Email-sender agent system prompt should…
- Writing email copy that will be rendered as HTML — covers the paragraph/heading/link block model
- SKILL.md covers The block model, Formatting rules, Tone and Recipient sourcing
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Composing Emails is an agent skill from friday-platform/friday-studio. General styling and tone guidelines for composing HTML emails. Use when writing email copy that will be rendered as HTML — covers the paragraph/heading/link block model, tone, subject lines, and how to handle data, URLs, and emphasis without markdown.
Its SKILL.md is about 650 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Agent Harness Platform — shareable workspaces, MCP tools, skills, memory, and cron/webhook automations. Self-hosted and transparent.
When your agent uses it
- Writing email copy that will be rendered as HTML — covers the paragraph/heading/link block model
- How to handle data
- Emphasis without markdown
Example prompts
- “/composing-emails”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Signal schema declares the recipient as a required field — caller can't trigger the job without it.
- Action prompt interpolates from the signal payload (works in any step, including ones with inputFrom — see writing-workspace-jobs →…
- Email-sender agent system prompt should refuse rather than guess: "If the recipient address contains an unresolved {{...}} placeholder or…
What it can do on your machine
Read from SKILL.md and the folder at commit fb3069a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Composing Emails loads about 648 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 280 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 280 words (~648 tokens).
“Emit content as an array of { tag, content } blocks. Only three tags exist:”
- name
- composing-emails
Files
Just SKILL.md in packages/system/skills/composing-emails of friday-platform/friday-studio.
Open the folder on GitHubat commit fb3069a
Compare with similar skills
Composing Emails next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Composing Emails this skillfriday-platform/friday-studio | 104 | — | ~648 | Automated safety check: Pass | Custom licence | |
| Emailasgeirtj/system_prompts_leaks | 69k | — | ~3.5k | Automated safety check: Pass | CC0-1.0 | |
| Emailscoreyhaines31/marketingskills | 54k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Mailtrap Email Integrationaffaan-m/ECC | 275k | 1 repos | ~955 | Automated safety check: Pass | MIT | |
| Email Marketing Biblesickn33/agentic-awesome-skills | 47k | — | ~8.7k | Automated safety check: Pass | MIT | |
| Email Systemsdavila7/claude-code-templates | 32k | 2 repos | ~548 | Automated safety check: Pass | MIT |
Similar skills
Email
Emails
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.
Mailtrap Email Integration
affaan-m/ECC
Guides agents through integrating transactional email sending via Mailtrap's Email API, including sandbox testing, domain verification, and API authentication.
Email Marketing Bible
sickn33/agentic-awesome-skills
Data-backed email marketing for AI agents: automation flows, deliverability triage, copy de-slopping, AI email design, ESP control via MCP with send gates and compliance.
Email Systems
davila7/claude-code-templates
Email has the highest ROI of any marketing channel. An agent skill from davila7/claude-code-templates.
- Official
Email Drafter
github/awesome-copilot
Draft and review professional emails that match your personal writing style.
More from friday-platform/friday-studio
All 20 skills in this repoAuthoring Skills
friday-platform/friday-studio
Authors new agent skills that follow the Anthropic + agentskills.io specification.
Friday CLI
friday-platform/friday-studio
Interacts with a running Friday daemon via CLI and HTTP — lists/creates/modifies workspaces, triggers signals, watches sessions, publishes skills and agents.
Workspace API
friday-platform/friday-studio
Create, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYDURL.
Writing Workspace Signals
friday-platform/friday-studio
Authors Friday workspace signals with correct provider configs, payload schemas, and runtime wiring.
Repairing Workspaces Agents
friday-platform/friday-studio
Repairs and upgrades existing Friday workspaces, jobs, user agents, and generated agents to current runtime contracts.
Using Elicitations
friday-platform/friday-studio
Asks the user mid-run from inside an FSM action or Python type: user agent via the elicitation tools — requesttoolaccess for allowlist approvals and requesthumaninput for HITL (human-in-the-loop)…
Questions about Composing Emails
What does Composing Emails do?
General styling and tone guidelines for composing HTML emails. Composing Emails is an agent skill from friday-platform/friday-studio. General styling and tone guidelines for composing HTML emails.
When should I use Composing Emails?
Composing Emails fits situations like: writing email copy that will be rendered as HTML — covers the paragraph/heading/link block model; how to handle data; emphasis without markdown.
How do I install Composing Emails in Claude Code?
Run `npx skills add friday-platform/friday-studio --skill composing-emails -a claude-code`. Or copy the skill folder (packages/system/skills/composing-emails in friday-platform/friday-studio) into .claude/skills/composing-emails in your project. Claude Code loads it when a task matches its description.
How do I install Composing Emails in Codex?
Run `npx skills add friday-platform/friday-studio --skill composing-emails -a codex`. Or copy the skill folder (packages/system/skills/composing-emails in friday-platform/friday-studio) into .agents/skills/composing-emails in your project. Codex loads it when a task matches its description.
Can I use Composing Emails in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add friday-platform/friday-studio --skill composing-emails -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/composing-emails, .gemini/skills/composing-emails, .github/skills/composing-emails and .opencode/skills/composing-emails in your project.
What does Composing Emails need to run?
SKILL.md names no scripts, command-line tools or credentials: Composing Emails is instructions for the agent only.
Does Composing Emails access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Composing Emails safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Composing Emails use?
Composing Emails has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Composing Emails use?
About 648 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Composing Emails?
Skills that share tags, products or a category with Composing Emails: Email (asgeirtj/system_prompts_leaks, 69k stars), Emails (coreyhaines31/marketingskills, 54k stars), Mailtrap Email Integration (affaan-m/ECC, 275k stars) and Email Marketing Bible (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Composing Emails?
friday-platform (a GitHub organization) maintains it in friday-platform/friday-studio, which has 104 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 5, 2026.
Source: friday-platform/friday-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.