Skip to content

[workshop-sync] workshop/side-quest-29-01-skill-injection-strategies.md: inline skill example missing required description frontmatter #3401

Description

@github-actions

Workshop file reviewed

workshop/side-quest-29-01-skill-injection-strategies.md

Problem

The "Inline" strategy example is missing the required skill frontmatter block. The file shows:

## skill: `issue-triage`

Classify each issue as `bug`, `feature`, or `question` based on its title and body.
For issues classified as `bug`, confirm the body includes steps to reproduce,
expected vs. actual behavior, and environment details.

Current correct syntax

Per gh-aw's skills.md reference (linked from the custom-agent-for-aw docs page), an inline skill block requires a ----delimited frontmatter section with at least a description: field immediately after the ## skill: \name`` heading, before the skill body:

## skill: `issue-triage`
---
description: Classify issues and suggest next actions.
---
Classify each issue as `bug`, `feature`, or `question` based on its title and body.
For issues classified as `bug`, confirm the body includes steps to reproduce,
expected vs. actual behavior, and environment details.

Without the --- frontmatter block containing description:, the inline skill extraction step may not parse the block correctly. (The hint, fusion, and other syntax in this file — gh-skill-fusion: comments, .github/skills/ discovery paths, and "unpinned-skill" compiler warnings — were all verified accurate against gh-aw's docs and do not need changes.)

Suggested fix

Add the ---\ndescription: <one-line summary>\n--- frontmatter block to the inline skill code example, matching the documented pattern.

Generated by 🔍 Workshop Sync Check · copilot · auto · 283.8 AIC · ⌖ 6.14 AIC · ⊞ 8.6K ·

  • expires on Sep 16, 2026, 11:51 AM UTC

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions