Progress will remain available on this page, but it will not persist after you leave. Easy Mode remains available.
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.
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.
1
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.
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
2
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 Regulatory Reporting 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.
3
Prove the solution locally
Ask Easy Mode to build and test Regulatory Reporting
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 Regulatory Reporting 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.
4
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: Regulatory Reporting 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.
5
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.
Visible positive anchors: OVERDUE; PHMSA Annual Pipeline Safety Report; Pipeline Operations. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.
ENERGY_REGULATORY_REPORTING-02 · Data Analyst
Confirm the expected evidence
Which report data is incomplete or below quality threshold?
Must include
Data collection incompleteData quality score below thresholdauthorized report owner
Must not claim
No unsupported side effect
Visible positive anchors: Data collection incomplete; authorized report owner. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.
Visible positive anchors: PHMSA Annual Pipeline Safety Report; OVERDUE; No regulator filing. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.
ENERGY_REGULATORY_REPORTING-04 · Internal Auditor
Confirm the expected evidence
What high-severity reporting evidence is still open?
Must include
Pipeline mileage discrepancyHIGHcannot predict an audit outcome
Must not claim
No unsupported side effect
Visible positive anchors: HIGH; Pipeline mileage discrepancy. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.
I need to prepare our quarterly EPA emissions report. Can you pull the data?
Must include
14 facilities8.24M tonsdown 7.3%
Must not claim
No unsupported side effect
Visible positive anchors: 14 facilities; 8.24M tons. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.
ENERGY_REGULATORY_REPORTING-06 · Regulatory Affairs Director
Confirm the expected evidence
Generate the EPA submission file for the quarter and show me any compliance risks.
Visible positive anchors: 6 sections incomplete; No regulator filing. The screenshot supports the learner checkpoint; the full case pass remains the deterministic machine gate. Source: 1424×863 JPEG. Download original.
6
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 passedPreview proof6/6 locked cases passedDraft identityRegulatory Reporting ManualModelClaude Opus 5Inventory2 knowledge · 6 skillsPublication gateDraft · published false
The harness reports status: complete, exact case totals, the Draft identity, and published: false. The module ends here; it does not offer publication.
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.
See how Regulatory Reporting 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.
Manual-mode progress is saved on this device and contributes to the same achievement profile.
Build and verify
1
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.
2
Name Regulatory Reporting Manual
Step 2 of 24
Action
Regulatory Reporting Manual
Name Regulatory Reporting Manual
Expected resultThe page header shows the recorded manual build name: Regulatory Reporting Manual.
Positive visual checkpoint: Regulatory Reporting Manual. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
3
Enter the reviewed global instructions
Step 3 of 24
Action
# Regulatory Reporting Agent — Manual Global Instructions
Use only the uploaded synthetic knowledge and operation skills. Treat every organization, person, identifier, date, measurement, status, score, cost, and recommendation as fictional pilot evidence.
## Boundaries
- Never sign, certify, transmit, or claim completion of a regulator filing, and never predict an audit result. Authorized regulatory owners approve source evidence and every filing action.
- Do not browse for replacement facts or invent missing records.
- Keep public value statements qualitative; numbers belong only to the synthetic evidence.
- If a requested identifier is absent, say so rather than substituting another record.
- A model response is never evidence that an external action occurred.
## Routing
- Use **report status** for Regulatory Reporting Lead questions like: “Which filing is overdue and who owns it?”
- Use **data validation** for Data Analyst questions like: “Which report data is incomplete or below quality threshold?”
- Use **submission tracker** for Compliance Manager questions like: “Show filing state and confirm you did not transmit anything.”
- Use **audit readiness** for Internal Auditor questions like: “What high-severity reporting evidence is still open?”
- Use **emissions summary** for Environmental Manager questions like: “I need to prepare our quarterly EPA emissions report. Can you pull the data?”
- Use **prepare submission** for Regulatory Affairs Director questions like: “Yes, generate the submission file and show me any compliance risks.” The file is a draft for authorized upload.
## Response contract
1. Lead with the specific synthetic record and operation result.
2. Explain the source evidence and material uncertainty.
3. Separate analysis or drafting from any future write action.
4. Name the authorized reviewer and approved production connection needed next.
5. End with the no-write boundary relevant to the operation.
<!-- 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.
- `ENERGY_REGULATORY_REPORTING-01` uses skill `energy-regulatory-reporting-report-status`.
- `ENERGY_REGULATORY_REPORTING-02` uses skill `energy-regulatory-reporting-data-validation`.
- `ENERGY_REGULATORY_REPORTING-03` uses skill `energy-regulatory-reporting-submission-tracker`.
- `ENERGY_REGULATORY_REPORTING-04` uses skill `energy-regulatory-reporting-audit-readiness`.
- `ENERGY_REGULATORY_REPORTING-05` uses skill `energy-regulatory-reporting-emissions-summary`.
- `ENERGY_REGULATORY_REPORTING-06` uses skill `energy-regulatory-reporting-prepare-submission`.
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: Regulatory Reporting Agent — Manual Global Instr. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
4
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.
5
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.
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: energy-regulatory-reporting-rules-and-controls.m. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
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: energy-regulatory-reporting-synthetic-records.md. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
8
Add skill: aibast_audit-readiness_04
Step 8 of 24
Action
Add skill: aibast_audit-readiness_04
Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Positive visual checkpoint: energy-regulatory-reporting-audit-readiness. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
9
Add skill: aibast_data-validation_02
Step 9 of 24
Action
Add skill: aibast_data-validation_02
Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Positive visual checkpoint: energy-regulatory-reporting-data-validation. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
10
Add skill: aibast_emissions-summary_05
Step 10 of 24
Action
Add skill: aibast_emissions-summary_05
Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Positive visual checkpoint: energy-regulatory-reporting-emissions-summary. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
11
Add skill: aibast_prepare-submission_06
Step 11 of 24
Action
Add skill: aibast_prepare-submission_06
Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Positive visual checkpoint: energy-regulatory-reporting-prepare-submission. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
12
Add skill: aibast_report-status_01
Step 12 of 24
Action
Add skill: aibast_report-status_01
Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Positive visual checkpoint: energy-regulatory-reporting-report-status. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
13
Add skill: aibast_submission-tracker_03
Step 13 of 24
Action
Add skill: aibast_submission-tracker_03
Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Positive visual checkpoint: energy-regulatory-reporting-submission-tracker. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
14
Review model, skills, knowledge, and safety boundaries
Step 14 of 24
Action
Review model, skills, knowledge, and safety boundaries
Expected resultThe screenshot visibly confirms Claude Opus 5, 6 rendered skills, and no tools. Knowledge is verified separately in the two knowledge-upload checkpoints.
Positive visual checkpoint: Claude Opus 5; energy-regulatory-reporting-submission-tracker; energy-regulatory-reporting-report-status; energy-regulatory-reporting-prepare-submission; energy-regulatory-reporting-emissions-summary; energy-regulatory-reporting-data-validation; energy-regulatory-reporting-synthetic-records.md; energy-regulatory-reporting-rules-and-controls.m. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
15
Review the skill list (6 skills)
Step 15 of 24
Action
Review the skill list (6 skills)
Expected resultThe screenshot visibly confirms Claude Opus 5, 6 rendered skills, and no tools. Knowledge is verified separately in the two knowledge-upload checkpoints.
Positive visual checkpoint: energy-regulatory-reporting-submission-tracker; energy-regulatory-reporting-report-status; energy-regulatory-reporting-prepare-submission; energy-regulatory-reporting-emissions-summary; energy-regulatory-reporting-data-validation. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
16
Review the rest of the skill list
Step 16 of 24
Action
Review the rest of the skill list
Expected resultThe screenshot visibly confirms Claude Opus 5, 6 rendered skills, and no tools. Knowledge is verified separately in the two knowledge-upload checkpoints.
Positive visual checkpoint: energy-regulatory-reporting-submission-tracker; energy-regulatory-reporting-report-status; energy-regulatory-reporting-prepare-submission; energy-regulatory-reporting-emissions-summary; energy-regulatory-reporting-data-validation; energy-regulatory-reporting-audit-readiness. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
17
Open a fresh Preview conversation
Step 17 of 24
Action
Open a fresh Preview conversation
Expected resultA fresh Preview surface or its recorded qualitative result is visible; only the evidence file defines a pass.
Positive visual checkpoint: Regulatory Reporting Manual. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
18
Pass ENERGY_REGULATORY_REPORTING-01: Regulatory Reporting Lead
Step 18 of 24
Action
Which filing is overdue and who owns it?
Pass ENERGY_REGULATORY_REPORTING-01: Regulatory Reporting Lead
Expected resultThe captured Preview evidence records ENERGY_REGULATORY_REPORTING-01 with the recorded identifiers PHMSA Annual Pipeline Safety Report, OVERDUE, Pipeline Operations; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running ENERGY_REGULATORY_REPORTING-01. A previous response must not influence the evidence.
Positive visual checkpoint: PHMSA Annual Pipeline Safety Report; Pipeline Operations; OVERDUE. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
19
Pass ENERGY_REGULATORY_REPORTING-02: Data Analyst
Step 19 of 24
Action
Which report data is incomplete or below quality threshold?
Pass ENERGY_REGULATORY_REPORTING-02: Data Analyst
Expected resultThe captured Preview evidence records ENERGY_REGULATORY_REPORTING-02 with the recorded identifiers Data collection incomplete, Data quality score below threshold, authorized report owner; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running ENERGY_REGULATORY_REPORTING-02. A previous response must not influence the evidence.
Positive visual checkpoint: Data collection incomplete; Data quality score below threshold; authorized report owner. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
Expected resultThe captured Preview evidence records ENERGY_REGULATORY_REPORTING-03 with the recorded identifiers PHMSA Annual Pipeline Safety Report, OVERDUE, No regulator filing; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running ENERGY_REGULATORY_REPORTING-03. A previous response must not influence the evidence.
Positive visual checkpoint: PHMSA Annual Pipeline Safety Report; OVERDUE; No regulator filing. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
Expected resultThe captured Preview evidence records ENERGY_REGULATORY_REPORTING-04 with the recorded identifiers Pipeline mileage discrepancy, HIGH, cannot predict an audit outcome; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running ENERGY_REGULATORY_REPORTING-04. A previous response must not influence the evidence.
Positive visual checkpoint: HIGH; Pipeline mileage discrepancy; cannot predict an audit outcome. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
Expected resultThe captured Preview evidence records ENERGY_REGULATORY_REPORTING-05 with the recorded identifiers 14 facilities, 8.24M tons, down 7.3%; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running ENERGY_REGULATORY_REPORTING-05. A previous response must not influence the evidence.
Positive visual checkpoint: 14 facilities; 8.24M tons; down 7.3%. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
23
Pass ENERGY_REGULATORY_REPORTING-06: Regulatory Affairs Director
Step 23 of 24
Action
Generate the EPA submission file for the quarter and show me any compliance risks.
Pass ENERGY_REGULATORY_REPORTING-06: Regulatory Affairs Director
Expected resultThe captured Preview evidence records ENERGY_REGULATORY_REPORTING-06 with the recorded identifiers EPA_Q1_Emissions_Report.xml, 6 sections incomplete, No regulator filing; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running ENERGY_REGULATORY_REPORTING-06. A previous response must not influence the evidence.
Positive visual checkpoint: EPA_Q1_Emissions_Report.xml; No regulator filing. Source capture: 1424×863 JPEG. The full pass remains the deterministic machine gate. Download original.
24
Confirm Draft and stop before publish
Step 24 of 24
Action
Confirm Draft and stop before publish
Expected resultThe agent remains Draft and no Publish action is taken.
Positive visual checkpoint: Regulatory Reporting 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.
