Sergo Examples

Optional Sergo examples for cache formats and reporting templates.

1 minute · 31 words · 4 sections

Use this skill only when Sergo needs concrete format examples.

Example: cached tools snapshot

{
  "last_updated": "2026-01-15T12:00:00Z",
  "tools": [
    {"name": "tool-name-1", "description": "..."},
    {"name": "tool-name-2", "description": "..."}
  ]
}

Example: strategy history entries

{"date": "2026-01-14", "strategy": "symbol-analysis", "tools": ["find-symbol", "get-definition"], "findings": 3, "tasks_created": 2, "success_score": 8}
{"date": "2026-01-13", "strategy": "type-inspection", "tools": ["get-hover", "get-type"], "findings": 5, "tasks_created": 3, "success_score": 9}

Example: task template

### Task [N]: [Short Title]

**Issue Type**: [Symbol Analysis / Type Inspection / etc.]
**Problem**: [Clear description]
**Location(s)**: [file paths and line references]
**Impact**: Severity, affected files, risk
**Recommendation**: [Specific fix]
**Validation**: Existing tests, Serena verification, related-pattern check, docs if needed
**Estimated Effort**: [Small/Medium/Large]

Example: discussion structure

Follow the reporting skill (headers ###+, <details> for long sections):

### 🔬 Sergo Report: [Strategy Name]

**Date**: [YYYY-MM-DD]
**Strategy**: [Name]
**Success Score**: [X/10]

### Executive Summary
### 🛠️ Serena Tools Update
### 📊 Strategy Selection
### 🔍 Analysis Execution

<details>
<summary><b>📋 Detailed Findings</b></summary>
</details>

### ✅ Improvement Tasks Generated
### 📈 Success Metrics

<details>
<summary><b>📊 Historical Context</b></summary>
</details>

### 🎯 Recommendations
### 🔄 Next Run Preview

Credited

This skill is installed in github/gh-aw — in use here rather than published from here — so there is no install command for it on this page.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/github/gh-aw, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

54 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 4 distinct layouts observed: .claude/skills/*/SKILL.md, .github/skills/*/SKILL.md, .squad/*/skill.md, SKILL.md (repo root).

Authorship

27 of 54 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 295°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

None needed in this skill: the outline was already valid.

Spec compliance

4 editorial notes across 3 of 54 skills. They are printed in the margin of each skill rather than as errors here.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /github/gh-aw.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.