Give your Agent a course studio.
This is the general PersonWise Skill: turn a topic or supplied materials into a complete course, then review, refine, configure, and publish it without leaving your Agent.
Public contract
- Skill version
- v1.0.0
- Authorization
- OAuth 2.1 + PKCE
- Connection
- Streamable HTTP
Install
One command. No private package.
The Skill is public, lightweight, and versioned in GitHub. The course engine, permissions, and commercial rules stay on PersonWise.
$ npx skills add personwiseai/skills --skill personwise-create-courseThe same Skill package works in conforming Agent Skill hosts. It connects to the same remote MCP without a host-specific workflow.
Inspect the public source at personwiseai/skills
General workflow
The complete course-creation loop.
The Skill coordinates the whole authoring job while the shared MCP exposes the authenticated operations.
- 01
Create from a topic or materials
Set the learner, outcome, source boundary, language, length, and course structure.
- 02
Review every authoring stage
Inspect outlines, visible page text, narration, and visual direction before advancing.
- 03
Refine without starting over
Update specific pages, narration, presenter choices, layout, or generated images.
- 04
Resume and finish safely
Continue durable runs, recover supported failures, and publish only within the approved OAuth ceiling.
One OAuth connection for every PersonWise Skill.
PersonWise never asks you to paste an API key or access token. The Agent keeps its own PKCE state and credential store; you choose the organization, course allowance, capabilities, and publication ceiling on PersonWise.
- 01Install the Skill in a conforming Agent host.
- 02Ask it to create or work on a PersonWise course. The Agent discovers the protected MCP endpoint and opens PersonWise authorization.
- 03Sign in to PersonWise, review the exact access request, and approve. The Agent resumes automatically.
OAuth-protected MCP endpoint
https://mcp.personwise.ai/mcpOAuth must begin inside the Agent so the authorization returns to that same client. Never paste an authorization code or token into chat.
Shared execution
One Skill now. One MCP throughout.
Future scenario Skills will narrow the workflow for a specific job. They will keep this same endpoint, authorization model, and course capability contract.