The pdu-claim-info skill: turn learning content into PDU claims with Claude

What it is, and why "agentic" matters

A Claude skill is a set of standing instructions saved as a file. You write the process once (or install one someone else wrote), and Claude applies it automatically whenever your request matches. That is the practical difference between a chatbot and an agent: instead of you prompting step by step, the agent recognizes the work, runs a multi-step process, and hands you a finished product.

pdu-claim-info encodes the process of a careful continuing-education advisor. Give it any professional learning content and it evaluates the material against all three PMI Talent Triangle categories (Ways of Working, Power Skills, Business Acumen), rates each with evidence, proposes claiming options on the standard 0.25 / 0.5 / 0.75 / 1.0 PDU scale, and drafts the CCRS entry with APA citations. You do not even need to ask about PDUs: submitting the content is the trigger.

Get the skill

GitHub · free and open source

The skill lives in the kasey6801/claude-skills repository, alongside its documentation, install instructions, and a packaged one-file bundle.

Get pdu-claim-info on GitHub →

Option A: install the packaged .skill bundle

One file. Download it and open it in your Claude client (Claude Code or Cowork) to install.

curl -L -o pdu-claim-info.skill \
  https://github.com/kasey6801/claude-skills/raw/main/skills/dist/pdu-claim-info.skill

Option B: copy the source folder into a project

Installs for the current project only. Use ~/.claude/skills instead to make it available everywhere.

mkdir -p .claude/skills
git clone --depth 1 https://github.com/kasey6801/claude-skills.git /tmp/cs \
  && cp -r /tmp/cs/skills/pdu-claim-info .claude/skills/ \
  && rm -rf /tmp/cs

Either way the skill ends up at .claude/skills/pdu-claim-info/SKILL.md. It is then available as /pdu-claim-info and also triggers automatically when you submit learning content. No API keys, no configuration, nothing to run.

Use it in four steps

Drop learning content into a Claude conversation.
A video transcript, an article, a course description, podcast episode notes, a conference session abstract, or just a sentence saying what you read or watched. No special format, no explicit PDU question needed.
- Paste a transcript"Here's the transcript of a webinar I watched: [paste]"
- Mention a reading"I just finished reading the PMI Standard for AI in PPPM, about 6 hours over the week."
- Ask directly"Can I claim PDUs for this podcast episode? [link or notes]"
Let the skill run.
Claude recognizes the content and triggers the skill on its own. On the very first run it also fetches the live PMI CCR Handbook, saves the requirements to memory, and prompts you to refresh them once per calendar year, so the guidance tracks the current rules instead of stale training data.
Save the analysis as a knowledge asset.
After every analysis the skill offers to turn it into a file you keep. You choose the format and the file type:
- InfographicA visual one-pager: PDU breakdown, category strengths, and the top claiming option
- ReportA structured written document with every section of the analysis
- PresentationUp to 3 slides covering the key takeaways
Each is available as Markdown (.md), PDF (.pdf), or PowerPoint (.pptx). The first time you save one, the skill asks where assets should live (for example a PDU_Claims folder in your workspace), then remembers that folder and saves there automatically from then on. Files are named PDU_<content-slug>_<date>.<ext> so they sort chronologically, one folder of evidence per claim, ready for a PMI audit.
Review, pick an option, and file the claim yourself.
The report rates each Talent Triangle category, lays out claiming options with a plain statement of when each makes sense, and drafts the CCRS entry fields. It also flags anything it could not verify, like a video's upload date. You confirm those, pick an option, and submit at ccrs.pmi.org. The skill never touches CCRS: preparation is the agent's job, the claim is yours.

What every report contains

Section	What you get
Executive summary	Two to three sentences: what the content is and the primary PDU verdict
Category analysis	Ways of Working, Power Skills, and Business Acumen each rated Strong, Moderate, Weak, or None, with the specific segments that justify the rating
Claiming options	Three options (for example full split, single category, session-by-session) with PDU values on the 0.25 / 0.5 / 0.75 / 1.0 scale and the CCRS path
CCRS entry fields	Title, provider, description, and PDU value, ready to paste
Resources & citations	PMI CCR Handbook and CCRS links plus APA-formatted references
Verify-before-filing flags	Anything inferred rather than confirmed, called out explicitly

A real example

Output from an actual run, summarized. A 40-45 minute Stanford GSB leadership podcast went in; this came back:

Input: podcast panel · ~40-45 min

Think Fast, Talk Smart Live: Leadership Communication Panel

The skill rated Power Skills Strong (feedback frameworks, inviting dissent, listening), Ways of Working and Business Acumen Weak, and warned that stretching the weak categories "would be over-claiming." It recommended 0.75 PDU rather than a rounded-up 1.0, to match the actual runtime, and flagged the episode's publication date as unverified.

Verdict: 0.75 PDU · Power Skills · CCRS > Education > Self-Directed Learning

The same process handled a 297-page PMI standard (6.0 PDUs split across all three categories) and two hour-long webinars (1.0 PDU each, Business Acumen) on the same day: 8.75 audit-ready PDUs from one afternoon of pasting content.

The rules it works against

Certification	Cycle	Total PDUs	Minimum per category
PMP	3 years	60	8
PMI-ACP	3 years	30	4

Power Skills and Business Acumen PDUs count toward multiple PMI certifications at once if you hold more than one. Requirements per the PMI CCR Handbook; the skill keeps a live-fetched copy and refreshes it annually.

Turn learning content into PDU claims: the pdu-claim-info skill