Workflow Step Summaries Agent Skill
Write clear GitHub Actions step summaries with progressive disclosure.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/github/gh-aw --skill workflow-step-summariesThe instruction itself
5 sections, as written by the authorGitHub Actions Step Summary Guidance
Use this skill when generating content for $GITHUB_STEP_SUMMARY.
Structure summaries for quick scanning
- Start sections at
###(h3) for readable hierarchy in workflow run pages. - Keep titles plain text with no emojis.
- Put the most important status and outcomes first.
Use progressive disclosure
- Wrap detailed diagnostics, logs, and secondary data in HTML
<details>blocks. - Use a concise
<summary>line that states what the collapsed section contains. - Keep default-expanded content short; move verbose output into collapsible blocks.
Use Markdown for code and review output
- In
actions/github-script, prefercore.summary.*helpers to build summary content. - Use inline code with backticks for commands, paths, IDs, and config keys.
- Use fenced code blocks with a language tag for logs, diffs, snippets, or commands.
- Present review findings as markdown sections with clear severity and action items.
Suggested checklist before writing
- Confirm section headings start at h3.
- Confirm no title includes emoji.
- Confirm verbose content is inside
<details>blocks. - Confirm code and review content uses proper markdown code formatting.
Other skills for the same job
different authors, same section of the catalogue
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.
Multi-agent workflow examples to work together on the OpenServ Platform. Covers agent discovery, multi-agent workspaces, task dependencies, and workflow orchestration using the Platform Client. Read reference.md for the full API reference. Read openserv-agent-sdk and openserv-client for building and running agents.
> Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
Patterns for automating GitHub workflows with AI assistance, inspired by [Gemini CLI](https://github.com/google-gemini/gemini-cli) and modern DevOps practices.
Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
How to use it
Take github/workflow-step-summaries from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.