Evidence-grounded customer journey

Reporting Package Validation Agent

Build this agent step by step, then show it to a customer. Easy mode lets AI do the clicks; Manual mode shows every step yourself.

Get the one-pager and demo video Office hours All solutions

About this workshop

Workshop mission: Turn motivated, open-minded, non-technical sales professionals into AI superheroes who can match the practical output and problem-solving pace of technical peers who are not using AI, while staying evidence-grounded, governed, and honest about what the tools proved.

Boundary: synthetic qualitative evidence only—not a customer KPI, measured production result, live connection, or publication approval.

Found something inaccurate? Use Report an issue at that point. It opens a prefilled GitHub issue for review and does not submit anything automatically.

Self-paced local achievements

Workshop achievements

0 total points 0 in this workshop

0 of 0 Easy checkpoints complete

No badges yet

View achievements and local profile

Optional public verification

These points and badges are local, self-reported workshop progress—not externally verified proof or a capability claim.

This opens one prefilled progress issue containing every badge currently earned here. Nothing syncs until you submit it. Resubmitting later merges newly earned badge IDs without duplicate score, and one public issue submission opts your GitHub account into a public verified profile.

Workshop setup

Open GitHub Copilot Chat

Start in GitHub Copilot Chat. No Frontier desktop app is required; the Easy Mode skill handles any additional setup.

Get ready

Open VS Code with the GitHub Copilot Chat extension installed.
Sign in to GitHub with an account that has Copilot access.
Open the Copilot Chat panel and select Agent mode.

Expected result

GitHub Copilot Chat is open in VS Code, signed in, and set to Agent mode.

I opened GitHub Copilot Chat in Agent mode.

What you will learn

Use the single Easy Mode skill.
Build and prove the portable agent.
Deploy the reviewed solution as an unpublished Draft.
Confirm the behavior yourself in Copilot Studio Preview.
Recognize the evidence that means the module is complete.

Before you begin

Use VS Code with GitHub Copilot Chat in Agent mode.
Sign in to GitHub with Copilot access.
Have access to a Copilot Studio environment.
The skill handles setup for you.
Do not publish. This module ends with a validated Draft.

Easy mode

Prepare your Copilot

Brief your Copilot with one line

One skill owns discovery, testing, Draft deployment, and Preview validation.

Do this

Open GitHub Copilot Chat in VS Code and select Agent mode.
Paste this one line and send it. Copilot reads the skill itself; nothing to download.

Send this message

Go and read https://raw.githubusercontent.com/microsoft/aibast-agents-library/main/skills/aibast-easy-mode/SKILL.md and run the Reporting Package Validation workshop for me.

Expected result

Copilot says it has read the skill and is running the workshop. The skill owns the remaining setup and validation.

I sent the one line and Copilot started the workshop.

Prove the solution locally

Ask Easy Mode to build and test Reporting Package Validation

This step proves the portable business logic before any Copilot Studio work begins. The harness retrieves the immutable package, verifies the source, loads the agent, and runs every locked case.

Send this message

Give me Reporting Package Validation using Easy Mode and test it for me.

Expected result

Copilot reports a verified source and 6/6 locked local cases passed.

Copilot should end by suggesting the next message: Deploy it into Copilot Studio for me.

I saw every locked local case pass.

Create the reviewed Draft

Deploy the already-tested solution to Copilot Studio

The harness now uses the verified Microsoft Copilot Studio plugin to reuse or create the source-controlled Draft, synchronize the reviewed instructions and assets, validate the PAC project, and leave publication off.

Send this message

Deploy it into Copilot Studio for me.

Expected result

Draft: Reporting Package Manual
Model: Claude Opus 5
Knowledge files: 2
Skills: 6
Status: Draft; published: false

The harness then validates the real Preview front door before returning its final verdict.

I saw the Draft identity and unpublished state.

Verify the real experience

Confirm the Draft in Copilot Studio Preview

The harness already runs these checks automatically. Repeat them here so you understand what was proven and can recognize a correct result yourself.

Open the validated Draft.
Select Preview.
Choose New chat before each case.
Paste the exact prompt.
Compare the answer with the required and forbidden markers.

Open the Copilot Studio Draft ↗

Expected result

Every case passes in a fresh Preview conversation, and the agent still appears as Draft.

RPV-01 · FP&A Manager

Confirm the expected evidence

The June reporting package just landed. What did we receive and where did each file come from?

Must include

PKG-2026-066 files received11 of 12

Must not claim

I do not have accessI cannot help

Visible positive anchors: PKG-2026-06; 11 of 12. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.

The Preview response matched this contract.

RPV-02 · Financial Controller

Confirm the expected evidence

Run the integrity checks before anyone looks at the numbers.

Must include

2 blockingOutdoor ForecastA missing cell is not a zero

Must not claim

I do not have accessI cannot help

Visible positive anchors: 2 blocking; A missing cell is not a zero; Outdoor Forecast. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.

The Preview response matched this contract.

RPV-03 · FP&A Manager

Confirm the expected evidence

How did each division do against budget, and which variances need an explanation?

Must include

+$320K-7.6%offset each other

Must not claim

I do not have accessI cannot help

Visible positive anchors: +$320K; -7.6%; offset each other. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.

The Preview response matched this contract.

RPV-04 · FP&A Manager

Confirm the expected evidence

Does the driver bridge reconcile from budget to actual?

Must include

$10,760KUnexplained residualDoes not reconcile

Must not claim

I do not have accessI cannot help

Visible positive anchors: Does not reconcile; Unexplained residual; $10,760K. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.

The Preview response matched this contract.

RPV-05 · Financial Controller

Confirm the expected evidence

Route the exceptions to the right owners.

Must include

EX-01Consolidation leadnone has been sent

Must not claim

I do not have accessI cannot help

Visible positive anchors: EX-01; Consolidation lead; none has been sent. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.

The Preview response matched this contract.

RPV-06 · Finance Director

Confirm the expected evidence

Draft the executive summary for the leadership pack.

Must include

on budget overallIndustrial +$320Knot released

Must not claim

I do not have accessI cannot help

Visible positive anchors: on budget overall; Industrial +$320K; not released. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.

The Preview response matched this contract.

Recognize completion

Know what “done” looks like

The workshop is complete only when both the portable agent and the Copilot Studio front door prove the same behavior.

Local proof6/6 locked cases passed

Preview proof6/6 locked cases passed

Draft identityReporting Package Manual

ModelClaude Opus 5

Inventory2 knowledge · 6 skills

Publication gateDraft · published false

Positive visual checkpoint. Source: 1424×863 JPEG. Download original.

Final expected verdict

The harness reports status: complete, exact case totals, the Draft identity, and published: false. The module ends here; it does not offer publication.

I confirmed the final Draft verdict.

Troubleshooting

What you see	What it means	What to do
Copilot ignores the workshop	The wrong skill was read, or the chat began before the one line was sent.	Start a new Agent-mode chat and send the one line first.
Local validation is not 6/6	The portable source, package, or locked behavior does not match.	Stop. Do not deploy. Let the harness report the exact failed case and marker.
No active Copilot Studio environment	PAC has no selected environment.	Sign in or select the intended environment, then resend the deploy message.
The Draft already exists	The recorded schema is already in the environment.	The harness should clone and reconnect automatically. Treat an attendee choice prompt as a harness defect.
A Preview case misses a marker	The real front door does not match the reviewed contract.	Keep the case failed. Inspect instructions and assets; do not retry until it happens to pass.
The agent is Published	The workshop crossed its safety boundary.	Stop immediately. The module must end at Draft with `published: false`.

Facilitator evidence and portable download

These links support audit, troubleshooting, and offline delivery. They are not learner steps.

Field guide Locked evidence Evidence report Download audit manifest Download portable bundle Download Copilot Studio solution Deployment settings Export details Download generic workshop agent Download SKILL.md

Manual mode · see how it was built

See how Reporting Package Validation Agent is built, one capability at a time.

Optional. Easy mode already did all of this for you from one skill file. This path replays every action the AI took, one real browser frame per step, so you can understand the agent before you adapt it. No PAC CLI, YAML import, or plugin architect; stop at Draft.

Synthetic disclosure: this is qualitative workflow evidence using packaged synthetic inputs. It is not a customer KPI or a live-system result.

Found something inaccurate? Use Report an issue on that step. It opens a prefilled GitHub issue for review and does not submit automatically.

Open standalone Manual-mode guide ↗ Download source bundle Download Copilot Studio solution Deployment settings Export details

0 of 24 complete

Manual-mode progress is saved on this device and contributes to the same achievement profile.

Build and verify

Create a blank Copilot Studio agent

Step 1 of 24

Action

Create a blank Copilot Studio agent

Expected resultA blank Copilot Studio agent is visible in the captured Draft workspace.

Positive visual checkpoint: Untitled Agent. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.

Name Reporting Package Manual

Step 2 of 24

Action

Reporting Package Manual

Name Reporting Package Manual

Expected resultThe page header shows the recorded manual build name: Reporting Package Manual.

Positive visual checkpoint: Reporting Package Manual. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.

Enter the reviewed global instructions

Step 3 of 24

Action

# Reporting Package Validation Agent — Manual Global Instructions

You are a month-end reporting package validation pilot for finance teams. Explain the fixed synthetic snapshot and prepare
reviewable drafts without turning decision support into a decision.

## Fixed synthetic snapshot

- Use only the uploaded Reporting Package Validation synthetic records, rules, and 6
  packaged skills.
- Proseware Holdings and every record in the snapshot (one fictional June close package with six files, four divisions, three scenarios, a driver bridge and thresholds) are fictional and
  used only for demonstration. All names, identifiers, dates and amounts are invented.
- Do not browse, consult external sources, or add market, legal, regulatory, or
  current-date facts. Never invent a record, figure, owner, deadline, or result.
- Never match a fictional record to a real organization or person, or claim access
  to a live system.

## Natural-language routing

- Use **package intake and lineage** when someone asks what files the reporting package contains and where each one came from.
- Use **integrity checks** when someone wants completeness, missing-versus-zero, tie-out and formula checks run before the numbers are read.
- Use **variance against budget** when someone asks how each division did against budget and which variances need an explanation.
- Use **driver bridge reconciliation** when someone asks whether the budget-to-actual driver bridge reconciles.
- Use **exception routing** when someone wants the exceptions listed and routed to their owners.
- Use **executive summary draft** when someone asks for the draft executive summary or commentary for the leadership pack.

## Human and side-effect gates

- Never post a journal or adjustment; edit a division submission; release the reporting package; send commentary or owner requests; treat a missing value as zero.
- Division controllers own their submissions; the FP&A manager signs off before release.
- Present drafts as drafts and say that nothing was sent, submitted, or changed.

## Evidence-first response contract

1. Lead with the answer: the figure, record, table, or draft status that was asked for.
2. Keep the snapshot's identifiers, figures and tables exactly as recorded.
3. State the human review or approval needed next.
4. Make the synthetic and read-only limits explicit; never speculate.
5. End substantive answers with: **Synthetic finance review support only. No journal was posted, no submission was changed, and the package was not released.**

<!-- locked-preview-anchors:start -->
## Skill routing map

Route from the user's natural-language intent to the correct skill below. Do not narrate internal retrieval, tool selection, restrictions, or implementation mechanics; present only the user-facing result.

- `RPV-01` uses skill `package-intake`.
- `RPV-02` uses skill `integrity-checks`.
- `RPV-03` uses skill `variance-analysis`.
- `RPV-04` uses skill `driver-reconciliation`.
- `RPV-05` uses skill `exception-queue`.
- `RPV-06` uses skill `executive-summary`.

These skill names above are the ONLY valid skill identifiers. Never invent, guess, or reference any other skill name. If the correct skill or its knowledge cannot be loaded after one retry in the same turn, say so honestly and stop. Do not answer using values you already know from these instructions or from general knowledge -- a response with no real citation is not acceptable output.
<!-- locked-preview-anchors:end -->

Enter the reviewed global instructions

Expected resultThe reviewed manual/GLOBAL-INSTRUCTIONS.md policy is visible or saved without unrecorded edits.

Positive visual checkpoint: Reporting Package Validation Agent — Manual Glob. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.

Save the instruction policy

Step 4 of 24

Action

Save the instruction policy

Expected resultThe reviewed manual/GLOBAL-INSTRUCTIONS.md policy is visible or saved without unrecorded edits.

Positive visual checkpoint: Draft. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.

Remove default web search

Step 5 of 24

Action

Remove default web search

Expected resultThe captured inventory no longer lists the default web-search capability.

Positive visual checkpoint: Provide trusted context to guide decisions. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.

Add knowledge: aibast_reporting-package-validation-rules-and-guardrails.md

Step 6 of 24

Action

Add knowledge: aibast_reporting-package-validation-rules-and-guardrails.md

Expected resultThe exact knowledge file linked for this step is attached under its complete filename. Wait for processing to finish before continuing. This step does not require the final inventory or prove the other uploads.

Positive visual checkpoint: aibast_reporting-package-validation-rules-and-gu. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.

Add knowledge: aibast_reporting-package-validation-synthetic-records.md

Step 7 of 24

Action

Add knowledge: aibast_reporting-package-validation-synthetic-records.md

Positive visual checkpoint: aibast_reporting-package-validation-synthetic-re. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.

Add skill: aibast_driver-reconciliation_04

Step 8 of 24

Action

Confirm Draft and stop before publish

Expected resultThe agent remains Draft and no Publish action is taken.

Positive visual checkpoint: Reporting Package Manual. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.

Manual-mode troubleshooting

A screenshot or browserfilm frame is missing

Stop. Do not invent, recreate, or substitute an image. Capture the real frame, update the browserfilm manifest, and regenerate without --allow-pending.

A knowledge file is still processing

Wait for ingestion to finish before Preview. A partial answer is not evidence.

A skill upload fails

Use the linked raw SKILL.md. Fix the reviewed source deliberately; do not silently skip the action.

The model differs from Easy mode

Record the substitution and stop the parity claim until Easy and Manual use the same reviewed model.

The Preview answer misses an identifier

Mark the recorded case failed, inspect instructions and inventory, then replay the exact prompt in a fresh conversation.

Should I publish?

No. Keep this manual duplicate in Draft unless publication is separately approved. Do not choose Publish as part of this tutorial.