pm-aiwork
v1.0.0Working with AI, organisation-side: the questions every manager is asking this year. Audit whether the AI spend paid, redesign roles AI has changed, write a usable AI policy, review performance when output is AI-assisted, and clear the slop out of your content.
By Mohit AggarwalLicense: MIT1.4k GitHub starsUpdated yesterday
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Oct 4, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install pm-aiwork for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install pm-aiwork@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mohitagw15856/pm-claude-skillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/pm-aiwork/.
Plugin files
├── .claude-plugin/plugin.json├── skills/ai-assisted-performance-review/SKILL.md├── skills/ai-content-audit/SKILL.md├── skills/ai-roi-audit/SKILL.md├── skills/ai-usage-policy/SKILL.md└── skills/role-redesign-for-ai/SKILL.md
Included Skills5
Evaluate performance fairly when output is AI-assisted — what still measures the human, what now measures the tooling, and how to run the review conversation. Use when reviewing someone whose work is heavily AI-assisted, when output volume stopped meaning anything, when calibrating a team with uneven AI adoption, or when writing review criteria for the AI era. Produces review guidance: a what-measures-whom analysis, rewritten criteria, calibration rules for mixed-adoption teams, and conversation scripts. For the general review document use performance-review; for redesigning the role itself use role-redesign-for-ai.
Audit a content library, docs site, or blog for AI-generated filler that's eroding trust and search performance — and triage what to fix, rewrite, or delete. Use when asked to find slop in a content library, audit AI-written content quality, explain why content engagement or rankings dropped after scaling with AI, or set a quality bar for AI-assisted publishing. Produces an audited inventory with per-piece verdicts, the detection signals used, a triage plan, and a publishing quality gate that prevents recurrence. For a single article's AI-citability use aeo-optimizer; for the strategy itself use content-calendar or seo-content-brief.
Audit whether the organisation's AI spend actually paid — measured against baselines, not vendor math or vibes. Use when a CFO asks what the AI tools returned, when renewing AI contracts, when consolidating overlapping AI subscriptions, or to build the measurement plan before the next spend. Produces an ROI audit with per-tool verdicts (keep/consolidate/cut), the honest-measurement method behind each number, and a baseline plan for whatever can't be scored yet. To forecast ROI before an investment use roi-estimator; this skill measures what already happened.
Write an AI usage policy people can actually follow — approved tools, data rules, disclosure duties, and review obligations, in one page instead of legal fog. Use when asked for a company AI policy, acceptable-use rules for ChatGPT/Claude/Copilot at work, guidance on what data may go into AI tools, or to fix a policy nobody reads. Produces a one-page usable policy plus the decision log behind it. Not a substitute for legal advice; pairs with compliance-checklist for regulatory mapping and ai-ethics-review for system-level assessments.
Redesign a job role that AI now does a large part of — deliberately, instead of quietly expecting the same headcount to absorb 140% output. Use when AI has changed what a role spends time on, when writing a revised role charter or job description post-AI, when a team asks 'what is my job now', or when planning capacity after AI adoption. Produces a role redesign: the task inventory before/after, the redefined core of the role, new expectations and metrics, and the growth-path implications. For hiring rubrics use hiring-rubric; for org-wide skills planning use ai-upskilling or career-ladder-map.
Plugin manifests1
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "pm-aiwork",
"version": "1.0.0",
"description": "Working with AI, organisation-side: the questions every manager is asking this year. Audit whether the AI spend paid, redesign roles AI has changed, write a usable AI policy, review performance when output is AI-assisted, and clear the slop out of your content.",
"author": {
"name": "Mohit Aggarwal",
"email": "[email protected]"
},
"homepage": "https://github.com/mohitagw15856/pm-claude-skills",
"license": "MIT",
"keywords": [
"ai-adoption",
"policy",
"roi",
"performance",
"content-quality"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[pm-aiwork on Agent Plugins Marketplace](https://pluginsmp.com/plugins/pm-aiwork)