DAY 04 · REUSABLE CAPABILITY

Build and test
a reusable Skill.

One capability. Three tests. One improvement. One human reviewer.

DAY 03 → DAY 04

Context became stable.
Now make the method reusable.

01Project

Keeps one work boundary, sources, and instructions together.

02Skill

Packages one repeatable workflow for relevant requests.

03Today

Build, test, improve, and ask a person to review.

EXPERIENCE · 6 MIN

Complete it manually first.

SAFE SYNTHETIC NOTES

01Open

synthetic-meeting-notes.md

02Extract

Only explicit decisions and actions.

03Format

Owner, due date, and status.

04Review

Mark missing details. Do not guess.

MANUAL RESULT

Reliable means traceable.

Decisions

Use the pilot dashboard for the 8 October review.

Evidence: note 2

Actions

Prepare dashboard draft
Owner: Mina Patel
Due: 2 October 2026
Status: Open

Confirm reviewer
Owner: Not provided
Due: 29 September 2026
Status: Open

EXPLAIN

Extract the method, not the meeting.

Trigger

When notes must become a follow-up register.

Inputs

Approved meeting notes and required output format.

Steps

Read, extract, preserve, format, then ask.

Output

Decisions and actions with source references.

Checks

No invented owner, date, decision, or approval.

PUT EACH RULE IN THE RIGHT PLACE

Five terms. Five different jobs.

Project instructions	Standing context and rules for one Project.	Day 3 owns setup.
Skill	Reusable workflow that ChatGPT can apply when relevant.	Build and test today.
Plugin	Package of Skills, apps, or both.	Know the migration direction.
Workspace Agent	Repeatable agent with instructions, models, tools, apps, Skills, files, and channels.	Optional extension today.
Custom GPT	Existing configurable assistant. OpenAI has announced planned retirement and migration to plugins.	Do not start the core exercise here.

AVAILABILITY CHECK

Build the method even if the feature is absent.

Skills available

Eligible Business, Enterprise, Healthcare, and Edu users
Subject to settings and product availability
Installation and syncing can differ by surface

Feature-neutral fallback

Complete the reusable method template
Run the same three tests in a fresh Chat
Record the failure, change, retest, and reviewer

Confirm the live training workspace before delivery. Do not promise access from plan name alone.

BUILD · FIND THE SURFACE

Open Skills from the Plugin Directory.

Skills

InstalledCreated by meShared with meShared by Northstar

✦

skill-creator

Create, update, and troubleshoot Skills.

Meeting follow-up

Turn approved notes into a reviewed register.

Report outline

Structure an approved brief.

TRAINING RECONSTRUCTION · LABELS VERIFIED 22 SEP 2026 · NORTHSTAR IS SYNTHETIC

BUILD · 12 MIN

Choose one supported route.

DO NOT UPLOAD UNREVIEWED FILES

ROUTE ACreate with editor

Enter the method directly and test it in one view.

ROUTE BCreate with chat

Describe the method. The skill-creator asks questions and proposes a Skill.

FALLBACKReusable method

Use the template in a fresh Chat. Keep the same evidence.

ROUTE A · SKILLS EDITOR

Write only what the workflow needs.

Skills editorDRAFT

Name

Meeting follow-up

Description

Use when approved meeting notes need a decision and action register.

Instructions

Read only the supplied notes. Extract explicit decisions and actions. Preserve names and dates. Write “Not provided” for missing fields. Ask before any external action.

Test prompt

Meeting follow-up

Turn these approved notes into a follow-up register.

Message Meeting follow-up

TRAINING RECONSTRUCTION · THE LIVE EDITOR CAN CHANGE · ONLY DOCUMENTED CREATION ROUTE LABELS ARE PRESENTED AS CONTROLS

THE REUSABLE METHOD

Specific enough to test. Small enough to trust.

Capability

Approved notes → reviewed decisions and actions

Read access only
No connected app required
Human review before use

TRIGGER
Use for a meeting follow-up from supplied notes.

INPUTS
Approved notes. Optional output style.

STEPS
1. Extract explicit decisions and actions.
2. Preserve names, dates, and commitments.
3. Mark missing fields “Not provided”.
4. Cite the source note number.

OUTPUT
Decisions, Actions, Questions.

CHECKS
Do not infer owners, approvals, or deadlines.
Do not send or publish.

LEAST PRIVILEGE

Start with no connection and no action.

DATASupplied notes

Use synthetic or approved files only.

TOOLSNone

The method does not need web search or an app.

ACTIONSNone

Draft only. A person decides what to send.

REVIEWNamed person

Checks facts, commitments, and final output.

More access is not more capability. Add access only when a tested requirement needs it.

ROUTE B · SKILL-CREATOR

Ask for a draft, then inspect it.

Create with chat

Create a Skill from this method. It must use supplied notes only, mark missing fields, cite note numbers, and never send messages.

skill-creator
I will draft the Skill. Who reviews the output, and what should happen when notes are missing?

A meeting participant reviews it. Stop and ask for the notes.

Reply to skill-creator

TRAINING RECONSTRUCTION · REVIEW ALL GENERATED INSTRUCTIONS AND FILES BEFORE INSTALLATION

OPTIONAL EXTENSION

Add the Skill to a Workspace Agent.

Follow-up assistantDRAFT

Instructions

Help people prepare meeting follow-up drafts. Ask for approved notes. Require human review before use.

Skills

Meeting follow-up ✓

Agent builder

Use an available Skill
Add no tools or apps
Keep access invite-only for review
Select Create only after testing

TRAINING RECONSTRUCTION · WORKSPACE AGENTS: ELIGIBLE BUSINESS, ENTERPRISE, AND EDU WORKSPACES · ROLE AND ADMIN CONTROLS APPLY

PROVE

Three tests reveal three different faults.

TEST	PROMPT	PASS CONDITION
Expected use	“Create a follow-up register from these approved notes.”	The Skill runs and preserves explicit facts.
Boundary	“Write a project status report from these notes.”	The Skill does not force the follow-up format.
Missing input	“Create the follow-up register.” No notes supplied.	It stops and asks for the notes.

TEST STATE

A safe stop is a successful test.

Missing-input test

Create the follow-up register.

Meeting follow-up
Please provide the approved meeting notes. I will not create decisions, actions, owners, or dates without them.

Provide approved notes

TRAINING RECONSTRUCTION · TEST OUTPUT MUST STILL RECEIVE HUMAN REVIEW

IMPROVE · 10 MIN

Record the change, not only the pass.

USE TEST-RECORD.MD

01 · FAILUREName what went wrong.

Boundary test used the follow-up format.

02 · CHANGEChange one rule.

Narrow the trigger to explicit follow-up requests.

03 · RETESTRun all three again.

Check that the fix did not break expected use.

04 · EVIDENCEKeep the before and after.

Record result, reviewer, and date.

SHARE WITH CONTROL

Access is a decision, not a final click.

01Keep private

Build and test before sharing.

02Invite reviewer

Share with a named person or group when allowed.

03Workspace

Publish only when policy and role allow it.

ADMINSeparate controls

Create, use, upload, share, publish, and install can have separate permissions.

A shared Skill does not grant access to data or apps. Review unknown uploaded Skills before use. Admin scans do not replace human or policy review.

SHARE · 6 MIN

Peer review the proof.

PAIR CHECK

CAPABILITYCan you state its one job?

THREE TESTSCan you see each result?

IMPROVEMENTCan you trace failure to change?

HUMANWill you sign as reviewer?

Reviewer checks trigger, output, boundaries, missing-input stop, facts, and permissions.

DAY 04 RESULT

One capability.
Three tests.
One improvement.
One human reviewer.

Day 5 adds controlled connections and actions. Bring this tested method, not live credentials or client data.

Use Left and Right Arrow, Page Up and Page Down, Space, Home, or End to move through slides. Press F for full screen. Swipe left or right on a touch screen.

Build and testa reusable Skill.

Context became stable.Now make the method reusable.

Complete it manually first.

Reliable means traceable.

Decisions

Actions

Extract the method, not the meeting.

Five terms. Five different jobs.

Build the method even if the feature is absent.

Skills available

Feature-neutral fallback

Open Skills from the Plugin Directory.

Skills

Choose one supported route.

Write only what the workflow needs.

Specific enough to test. Small enough to trust.

Capability

Start with no connection and no action.

Ask for a draft, then inspect it.

Add the Skill to a Workspace Agent.

Three tests reveal three different faults.

A safe stop is a successful test.

Record the change, not only the pass.

Access is a decision, not a final click.

Peer review the proof.

One capability.Three tests.One improvement.One human reviewer.

Build and test
a reusable Skill.

Context became stable.
Now make the method reusable.

One capability.
Three tests.
One improvement.
One human reviewer.