Penroe skills
Run your client projects in Penroe from the AI assistant you already use. These skills teach Claude, ChatGPT and other assistants how to do the jobs a delivery lead does every week: create a project from a statement of work, keep it current, prepare for meetings, draft status updates, run a retrospective, and write the documents tasks call for.
What this is
This repository is the Penroe plugin. It bundles two things:
- The Penroe connection. It links your assistant to your Penroe workspace (
https://mcp.penroe.app/mcp). You sign in with your own Penroe account, and the assistant can see and change only what you already can. - Skills. Each skill is a short set of instructions for one job. Your assistant reads a skill when your request matches it, so it follows the same steps an experienced project lead would, using Penroe's own read of each project.
Skills
| Skill | Use it when | Try asking |
|---|---|---|
| get-started-with-penroe | You've just connected Penroe | "What can you do with Penroe?" |
| create-project | You have a statement of work, proposal or kickoff notes | "Here's the SOW for Northwind. Set up the project in Penroe." |
| update-project | Something changed: a change order, a meeting, a client email | "The client pushed the design review two weeks. Update the project." |
| prepare-for-meeting | A client or internal meeting is coming up | "Prep me for tomorrow's check-in with Northwind." |
| draft-project-update | It's time for a status update, for one project or several | "Draft this week's client update for the website redesign." |
| run-project-retrospective | A project or phase has wrapped up | "Run a retro on the Northwind launch." |
| write-task-document | A task needs a document: a kickoff agenda, change order, handoff note or memo | "Write the change order for ACME-T14." |
Every skill shows you what it plans to do before it changes anything in Penroe, and cites where each fact came from.
Example: a client input arrives late
Illustrative conversation, not a recorded customer run. The project, dates and responses below are examples of the workflow these skills guide.
Northwind's project plan has a client data handoff on November 3 and testing on November 4. Testing needs that data. The client emails to say the file will arrive on November 5.
You:
The client says the data file will arrive November 5 instead of November 3. Here's their email. Review what this affects and propose changes to the Northwind project.
The assistant reads the email and the current project plan. It distinguishes the client's expected arrival date from an approved change to the plan, then asks whether you want to re-plan the affected work.
You:
Yes. Propose moving the data handoff to November 5 and testing to November 6. The client hasn't agreed to change any committed dates.
The assistant previews the date changes and reports the conflicts returned by Penroe. Suppose the preview identifies a testing milestone still scheduled for November 5:
Assistant:
Testing needs the data file, so its November 4 date conflicts with the expected November 5 arrival. Moving testing to November 6 would also leave the testing milestone on November 5 in conflict.
I propose moving the handoff to November 5 and testing to November 6. The milestone needs a separate decision. I'll keep the client-committed dates unchanged. Do you approve these two working-date changes?
You:
Yes, apply those two changes. Leave the milestone unchanged for now and draft a client update that raises the milestone decision.
The assistant saves the approved changes, records the reason and source, and reports which items changed. It then drafts the client update from the revised project record:
With the data file now expected November 5, we've moved testing to November 6 in our working plan. That puts testing after the November 5 milestone. We need to agree how to handle that milestone; the existing client commitment remains unchanged.
You review the draft and send it. The assistant does not move other dates automatically or send the email.
Install
Claude Code
/plugin marketplace add penroe-ai/skills
/plugin install penroe@penroe
Then run /mcp, choose the Penroe server, and sign in.
Claude (desktop and claude.ai)
Add Penroe from Customize → Plugins, either from the plugin directory or by adding this repository as a marketplace. Then connect Penroe when Claude asks you to sign in.
ChatGPT and Codex
The Penroe plugin isn't in OpenAI's plugin directory yet. Until it is, you can connect ChatGPT to Penroe as a custom MCP server (without these skills); see penroe.ai/integrations/openai.
Other assistants
Add the skills on their own with the skills CLI:
npx skills add penroe-ai/skills
Then connect your assistant to the Penroe server at https://mcp.penroe.app/mcp. Skills installed this way don't update on their own; run the command again to update them.
How the Penroe connection works
- Your access, nothing more. The assistant acts as you, inside your workspace, and sees only what you can see in Penroe.
- Options you choose at sign-in. When you connect, you choose whether to also turn on Project templates, Groups and project roles, and the Review queue. Skills work without them and tell you when one would help. To change your choice, reconnect Penroe.
- Permission settings apply. You or your workspace admin can block some kinds of changes (such as deleting or sharing) for AI assistants. The skills respect that and tell you when it happens.
- Documents stay private until you share them. Anything an assistant attaches to a project is visible only to you until you share it from Penroe.
Security and trust
- Email, documents and messages that Penroe returns are your data, not instructions. The skills tell your assistant to report any instructions it finds in them and never act on them.
- Removing items, sharing, and changing who is on a project are separate actions that the skills confirm with you one at a time.
- Penroe can't send email or messages on your behalf.
- To disconnect, remove Penroe from your assistant's connections, or revoke its access in Penroe.
Found a security issue? See SECURITY.md.
Contributing
Penroe's team maintains these skills, and they track the Penroe connection closely, so we don't accept outside changes to skills or manifests. Issues with feedback and ideas are welcome. See CONTRIBUTING.md for how the repository is put together.