Skip to content

[skill-activity] Improve step 07: add YAML skeleton and expand checkpoint #2021

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 1 commit into from
Jul 25, 2026
+26 −2
Merged

[skill-activity] Improve step 07: add YAML skeleton and expand checkpoint #2021

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 26 additions & 2 deletions workshop/07-your-first-workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,28 @@ Compile it after creating it.

Review the agent's edit, then continue. Prefer this path over hand-editing each line.

**What the agent created** — the generated file should look roughly like this:

```yaml
---
name: Daily Report Status
on:
schedule:
- cron: "0 9 * * *" # runs every day at 09:00 UTC

@pelikhan pelikhan Jul 25, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot use fuzzy schedule like "daily"

workflow_dispatch: {} # also allows manual runs
permissions:
contents: read
issues: read
copilot-requests: write # required to call the AI model
safe-outputs:
- key: create-issue # the only write action the agent may perform

@pelikhan pelikhan Jul 25, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot check syntax

create-issue:

---

@github-actions github-actions Bot Jul 25, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incorrect safe-outputs syntax in the YAML skeleton.

The example shows:

safe-outputs:
  - key: create-issue         # the only write action the agent may perform

This is not valid safe-outputs frontmatter. The correct format is a map, not a list. All existing workflows in this repository use the map form:

safe-outputs:
  create-issue: {}

Suggested fix: replace - key: create-issue with create-issue: {}.

See all workflow files in .github/workflows/ for reference (e.g., curriculum-evaluator.md uses create-issue: as a map key).


Generate an activity report for this repository and post it as a new issue.
```

The **frontmatter** tells GitHub Actions when to run, what permissions the agent has, and which write action it may use (`create-issue`). The **task brief** below the second `---` is what the AI agent reads and acts on.

<picture>
<source media="(prefers-color-scheme: dark)" srcset="images/07a-workflow-dispatch-trigger-dark.svg">
<source media="(prefers-color-scheme: light)" srcset="images/07a-workflow-dispatch-trigger-light.svg">
Expand Down Expand Up @@ -69,9 +91,11 @@ For follow-up edits, keep using an agent with the `agentic-workflows` skill and

## ✅ Checkpoint

- [ ] `.github/workflows/daily-report-status.md` includes `permissions` with `copilot-requests: write`
- [ ] `gh aw compile` reports valid
- [ ] `.github/workflows/daily-report-status.md` exists and contains an `on: schedule:` trigger in the frontmatter
- [ ] The file includes `permissions` with `copilot-requests: write`
- [ ] `gh aw compile` exits with no errors and produces `daily-report-status.lock.yml`
- [ ] Both `daily-report-status.md` and `daily-report-status.lock.yml` are committed and pushed to `main`
- [ ] The workflow appears in the **Actions** tab of your repository under "Daily Report Status"
- [ ] You are ready to choose the workflow's billing and authentication method

<!-- journey: all -->
Expand Down
Loading