One-click install
npx skills add https://github.com/swghosh/ambient-workflows --skill summary-swghosh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summary
Source: https://github.com/swghosh/ambient-workflows/tree/main/workflows/operator-feature-dev/.claude/skills/summary
Command: npx skills add https://github.com/swghosh/ambient-workflows --skill summary-swghosh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It eliminates the effort of manually inspecting many generated workflow files by producing a single, high-signal status summary of what the operator feature development workflow has done.

Core Features & Use Cases

  • Artifact discovery across generated markdown outputs: Scans the operator-feature-dev artifacts directory for all generated markdown files (excluding the existing summary) to ensure coverage of what was actually produced.
  • Structured extraction of decisions, findings, and status: Organizes key information into Enhancement Proposal details, per-PR technical outputs, convention deviations, and outstanding items.
  • Actionable reporting with persistence: Presents a concise summary inline and writes the same deliverable to artifacts/operator-feature-dev/summary.md for later reference.

Quick Start

Ask the AI to run the summary skill to scan artifacts/operator-feature-dev/ and produce a concise Operator Feature Dev Summary with PR statuses, key findings, decisions, and outstanding concerns.

Frequently Asked Questions about summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a workflow summary from multiple operator feature development artifacts?

To generate a workflow summary from operator feature development artifacts, you can use a tool that scans the markdown files in your artifacts directory and extracts key PR findings and enhancement proposal details into a single structured status report.

What is an operator feature development summary and when do I need one?

An operator feature development summary is a synthesized status update extracted from multiple generated workflow markdown files. You need one when you must quickly review enhancement proposal decisions, PR outputs, and outstanding items without manually inspecting each file.

How do I extract pull request status and decisions from generated markdown artifacts?

Extracting pull request status and decisions from generated markdown artifacts involves reading workflow output files, excluding any existing summary, and organizing per-PR technical outputs, convention deviations, and enhancement proposal details into an actionable report.

Can I persist a generated artifact scanning report to a specific markdown file path?

Yes, you can persist a generated artifact scanning report by writing the final structured summary directly to a designated markdown file path, such as artifacts/operator-feature-dev/summary.md, ensuring the deliverable remains available for later reference.

Does artifact scanning for workflow summaries exclude existing summary files?

Yes, artifact scanning for workflow summaries explicitly excludes existing summary files like summary.md from the target directory to prevent circular referencing and ensure only newly generated enhancement proposal and PR artifacts are processed.

What's the best way to review enhancement proposal and code deliverables across multiple PR phases?

The best way to review enhancement proposal and code deliverables across multiple PR phases is to synthesize the generated workflow artifacts into a high-signal status update, aggregating per-PR technical outputs and outstanding concerns into one concise report.