Summarize Skill
Generate a human-readable summary page for a Claude Code skill. Reads the skill directory, checks for proprietary content, produces a Jekyll page following the site’s skill summary voice and structure, including a GitHub download link.
This skill is personalized to the Working With Machines site structure (Jekyll frontmatter, GitHub repo path, editorial voice). It is published as a demonstration of what a personalized operational skill looks like. Use personalize-skill to adapt it to your own site, repo and editorial conventions.
When to use
- Publishing a skill to the site — a new skill needs a summary page for human readers
- Updating a summary after skill changes — the skill evolved and the summary page is stale
When not to use
- Writing SKILL.md itself (that’s the skill author’s job)
- Reviewing or editing existing summary pages (use editorial review)
How it works
- Read the skill — SKILL.md plus any references, scripts and assets
- Proprietary analysis — classify each file as generic workflow (safe to publish), parameterized configuration (replace with template) or proprietary reasoning (generalize or exclude). Report classification to the user before proceeding.
- Generate the summary — one paragraph on what it does, when to use / not use, how it works (phases only, not implementation) and what it assumes (specific tools and integrations)
- Handle special cases — personal skills get framed as personalization demonstrations. Template skills get a Setup section listing which files need populating.
- Write the page — Jekyll frontmatter, GitHub link, structured sections
What it assumes
- Site repo structure — skills live in
skills/<name>/with summary pages atskills/<name>.md - GitHub repo —
bdauer/working-with-machineson themainbranch for download links - Jekyll — summary pages use Jekyll frontmatter with
parent: Skills - Editorial guide — skill summary voice rules in
.editorial-guide.md