New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Summary Style Guide

by provos in provos/ironcurtain

Tone and length conventions for email summaries — voice, verb tense, what to include vs omit, and target sentence count.

Apache-2.0Auto-check passedWriting & Content

Install Summary Style Guide

skills CLI
$ npx skills add provos/ironcurtain --skill summary-style-guide -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install provos/ironcurtain summary-style-guide --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/provos/ironcurtain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/workflow/workflows/test-email-summary/skills/summary-style-guide .claude/skills/summary-style-guide && rm -rf skills-src

Use ~/.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/

Facts

Skill name
summary-style-guide
GitHub stars
613
Token cost
~509 tokens
SKILL.md length
277 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

Tone and length conventions for email summaries — voice, verb tense, what to include vs omit, and target sentence count.

  • Writing & Content work in your project
  • SKILL.md covers Voice and tense, What to include, What to omit and Length, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Summary Style Guide is an agent skill from provos/ironcurtain. Tone and length conventions for email summaries — voice, verb tense, what to include vs omit, and target sentence count. Read this when writing the prose Summary line for each email so the voice is consistent across the report.

Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content. It works with Model Context Protocol. The repository describes itself as: A secure runtime for autonomous AI agents. Policy from plain-English constitutions. (https://ironcurtain.dev). The licence is Apache-2.0.

When your agent uses it

  • Writing & Content work in your project

Example prompts

  • “/summary-style-guide”

What it can do on your machine

Read from SKILL.md and the folder at commit d51a346. 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.

    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

Summary Style Guide loads about 509 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 277 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~509

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

The full file from provos/ironcurtain at commit d51a346, republished under its Apache-2.0 licence (© provos). 277 words, ~509 tokens.

Download SKILL.mdSave it as .claude/skills/summary-style-guide/SKILL.md (or your agent's skills folder).
name
summary-style-guide
description
Tone and length conventions for email summaries — voice, verb tense, what to include vs omit, and target sentence count. Read this when writing the prose Summary line for each email so the voice is consistent across the report.

Summary style guide

Each email in the report gets a one- or two-sentence prose summary. This document covers the voice of those sentences. For the surrounding markdown structure, the heading depth, and where the summary sits in the document, see the email-formatting conventions.

Voice and tense

  • Third-person, past tense. "Alice asked the team to review the deck" rather than "I am asking..." or "Alice is asking...".
  • Drop the salutation, the signature, and any thread quoting. The summary is what the email did, not how it was framed.
  • Active voice. "Bob declined the meeting" not "the meeting was declined by Bob".

What to include

The summary should answer: what is the actionable substance of this email? Concretely:

  • The ask, decision, or status update at the heart of the message.
  • Who is on the hook for what, if explicit.
  • Any deadline or date that anchors the action.

What to omit

  • Niceties ("Thanks!", "Hope you're well", "Cheers").
  • The sender's restatement of what they previously said in the thread.
  • Speculation about why the email was sent.
  • Any attachment list — that's separate metadata, not summary content.

Length

  • Prefer one sentence. Use two when the email genuinely covers two distinct items (e.g., a status update and an unrelated ask).
  • Hard cap: two sentences. If a summary feels like it needs three, the email contains multiple threads of substance and the summary should pick the most actionable one and drop the rest.

Confidence and hedging

If the email is ambiguous or the body is truncated, write a confident summary of what's visible rather than hedging. Do not insert "appears to" or "seems to be" — the consumer of the summary already knows it was machine-derived.

© provos, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/workflow/workflows/test-email-summary/skills/summary-style-guide of provos/ironcurtain.

Open the folder on GitHubat commit d51a346

Compare with similar skills

Summary Style Guide 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.

Summary Style Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Summary Style Guide this skillprovos/ironcurtain613—~509Automated safety check: PassApache-2.0
Writing Docsnukeop/nuclear19k—~907Automated safety check: PassAGPL-3.0
Zero Slopmanavmishra/ZeroSlop1321 repos~16kAutomated safety check: PassMIT
Social PostHao0321/claude-skill-social-post727—~2.9kAutomated safety check: PassMIT
China Travel Kittczyliu/china-travel-kit194—~1.3kAutomated safety check: PassMIT
Good Docs AuditComposioHQ/composio30k—~293Automated safety check: PassMIT

Similar skills

  • Writing Docs

    nukeop/nuclear

    A skill your agent uses when writing or editing documentation in packages/docs.

    19k GitHub stars~907 tokensUpdated 2 days ago
    Writing & ContentAuto-check passed

  • Zero Slop

    manavmishra/ZeroSlop

    Edit drafts into natural prose, inspect AI-sounding patterns, or review how a specified audience might respond passage by passage.

    132 GitHub starsUsed in 1 repo~16k tokens
    Writing & ContentAuto-check passed

  • Social Post

    Hao0321/claude-skill-social-post

    依使用者真實貼文與成效寫 Facebook／Instagram／YouTube／Threads／X 文案，包含 ChatGPT Chat 的「寫文」「Mode C」「用我的格式／口氣」「黑底白字」；本機工作台、規劃、確認後發布、留言回覆及成效學習。使用者說「發文」「文案」「Social Post 介面」「回覆留言」「查流量」「把數據訓練進去」「比較貼文」「優化 pattern」時使用。

    727 GitHub stars~2.9k tokensUpdated 5 days ago
    Writing & ContentAuto-check passed

  • China Travel Kit

    tczyliu/china-travel-kit

    Research and plan first-time independent trips in China with bilingual, source-aware city data and official live-check entry points.

    194 GitHub stars~1.3k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed

  • Good Docs Audit

    ComposioHQ/composio

    Audit a doc, guide, README, or block of prose against the good-docs-writing style guide and report violations.

    30k GitHub stars~293 tokensUpdated today
    Writing & ContentAuto-check passed

  • Release Blog Drafter

    obot-platform/obot

    Drafts a release announcement blog post for an obot release as a Markdown file, with an optional WordPress draft through MCP and no live publishing without confirmation.

    1.1k GitHub stars~4.6k tokensUpdated today
    Writing & ContentAuto-check passed

More from provos/ironcurtain

  • Harness Design Fuzzing

    provos/ironcurtain

    Reference vocabulary for designing instrumented harnesses that drive vulnerability discovery — design classes (trigger-driven vs coverage-driven), tiered scope (T1 isolated function / T2…

    613 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed

  • Email Formatting

    provos/ironcurtain

    Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer.

    613 GitHub stars~518 tokensUpdated yesterday
    Auto-check passed

  • Gmail Query Syntax

    provos/ironcurtain

    Reference for Gmail's search query syntax — operators like is:sent, newerthan:, from:, has:attachment, label:, and how they compose.

    613 GitHub stars~971 tokensUpdated yesterday
    Auto-check passed

  • JSON Schema Emails

    provos/ironcurtain

    Canonical shape of the .workflow/emails/emails.json file passed between the fetch and summarize states — required fields (sender, recipient, subject, date, body), types, and field semantics.

    613 GitHub stars~491 tokensUpdated yesterday
    Auto-check passed

  • Memory Safety C Cpp

    provos/ironcurtain

    Reference vocabulary for memory-safety vulnerabilities in native C/C++ code — bug-class taxonomy, common arithmetic patterns that lead to corruption, dispatch-family discipline, type-confusion…

    613 GitHub stars~5.6k tokensUpdated yesterday
    Auto-check passed

  • Vulnerability Triage

    provos/ironcurtain

    Reference vocabulary for interpreting vulnerability findings — detector-vs-impact distinction, severity anchoring on demonstrated evidence, the eleven-item interpretation rubric, delegation…

    613 GitHub stars~6.3k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Summary Style Guide

What does Summary Style Guide do?

Tone and length conventions for email summaries — voice, verb tense, what to include vs omit, and target sentence count. Summary Style Guide is an agent skill from provos/ironcurtain. Tone and length conventions for email summaries — voice, verb tense, what to include vs omit, and target sentence count.

When should I use Summary Style Guide?

Summary Style Guide fits situations like: writing & Content work in your project.

How do I install Summary Style Guide in Claude Code?

Run `npx skills add provos/ironcurtain --skill summary-style-guide -a claude-code`. Or copy the skill folder (src/workflow/workflows/test-email-summary/skills/summary-style-guide in provos/ironcurtain) into .claude/skills/summary-style-guide in your project. Claude Code loads it when a task matches its description.

How do I install Summary Style Guide in Codex?

Run `npx skills add provos/ironcurtain --skill summary-style-guide -a codex`. Or copy the skill folder (src/workflow/workflows/test-email-summary/skills/summary-style-guide in provos/ironcurtain) into .agents/skills/summary-style-guide in your project. Codex loads it when a task matches its description.

Can I use Summary Style Guide 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 provos/ironcurtain --skill summary-style-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/summary-style-guide, .gemini/skills/summary-style-guide, .github/skills/summary-style-guide and .opencode/skills/summary-style-guide in your project.

What does Summary Style Guide need to run?

SKILL.md names no scripts, command-line tools or credentials: Summary Style Guide is instructions for the agent only.

Does Summary Style Guide 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 Summary Style Guide 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 Summary Style Guide use?

Summary Style Guide is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Summary Style Guide use?

About 509 tokens (SKILL.md is roughly 2k 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 Summary Style Guide?

Skills that share tags, products or a category with Summary Style Guide: Writing Docs (nukeop/nuclear, 19k stars), Zero Slop (manavmishra/ZeroSlop, 132 stars), Social Post (Hao0321/claude-skill-social-post, 727 stars) and China Travel Kit (tczyliu/china-travel-kit, 194 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Summary Style Guide?

provos (a GitHub user) maintains it in provos/ironcurtain, which has 613 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.

Source: provos/ironcurtain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.