Cost Benefit
brycewang-stanford/Auto-Empirical-Research-Skills
Cost-benefit analysis. An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.
Produce a regulatory impact analysis (RIA) weighing the costs, benefits, and alternatives of a proposed rule.
MITAuto-check passed
Install Regulatory Impact Analysis
$ npx skills add mohitagw15856/pm-claude-skills --skill regulatory-impact-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills regulatory-impact-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/regulatory-impact-analysis .claude/skills/regulatory-impact-analysis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "regulatory-impact-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/regulatory-impact-analysis into .claude/skills/regulatory-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-impact-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/regulatory-impact-analysisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill regulatory-impact-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills regulatory-impact-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/regulatory-impact-analysis .agents/skills/regulatory-impact-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "regulatory-impact-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/regulatory-impact-analysis into .agents/skills/regulatory-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-impact-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill regulatory-impact-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills regulatory-impact-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/regulatory-impact-analysis .cursor/skills/regulatory-impact-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "regulatory-impact-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/regulatory-impact-analysis into .cursor/skills/regulatory-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-impact-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/regulatory-impact-analysis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill regulatory-impact-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills regulatory-impact-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/regulatory-impact-analysis .gemini/skills/regulatory-impact-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "regulatory-impact-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/regulatory-impact-analysis into .gemini/skills/regulatory-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-impact-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills regulatory-impact-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill regulatory-impact-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/regulatory-impact-analysis .github/skills/regulatory-impact-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "regulatory-impact-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/regulatory-impact-analysis into .github/skills/regulatory-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-impact-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill regulatory-impact-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills regulatory-impact-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/regulatory-impact-analysis .opencode/skills/regulatory-impact-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "regulatory-impact-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/regulatory-impact-analysis into .opencode/skills/regulatory-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "regulatory-impact-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
regulatory-impact-analysis- GitHub stars
- 1.4k
- Token cost
- ~1k tokens
- SKILL.md length
- 457 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Produce a regulatory impact analysis (RIA) weighing the costs, benefits, and alternatives of a proposed rule.
- Asked to assess a regulations impact
- SKILL.md covers Required Inputs, Output Format, Quality Checks and Anti-Patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Do a cost-benefit analysis of a policy
What it does
Regulatory Impact Analysis is an agent skill from mohitagw15856/pm-claude-skills. Produce a regulatory impact analysis (RIA) weighing the costs, benefits, and alternatives of a proposed rule. Use when asked to assess a regulation's impact, do a cost-benefit analysis of a policy, justify a rulemaking, or compare regulatory options. Produces a structured RIA: the problem and rationale, options including the baseline, costs vs. benefits, distributional effects, and a reasoned recommendation.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to assess a regulations impact
- Do a cost-benefit analysis of a policy
- Justify a rulemaking
- Compare regulatory options
Example prompts
- “/regulatory-impact-analysis”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Regulatory Impact Analysis loads about 1k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 457 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 457 words, ~1,006 tokens.
Download SKILL.mdSave it as
.claude/skills/regulatory-impact-analysis/SKILL.md (or your agent's skills folder).- name
- regulatory-impact-analysis
- description
- Produce a regulatory impact analysis (RIA) weighing the costs, benefits, and alternatives of a proposed rule. Use when asked to assess a regulation's impact, do a cost-benefit analysis of a policy, justify a rulemaking, or compare regulatory options. Produces a structured RIA: the problem and rationale, options including the baseline, costs vs. benefits, distributional effects, and a reasoned recommendation.
Regulatory Impact Analysis Skill
Before a rule is made, good practice (and often law) requires showing it's justified: what problem it solves, what it costs, what it delivers, and whether a lighter option would do better. This skill produces a structured RIA — honest about uncertainty, comparing real alternatives against the do-nothing baseline.
Educational analytical aid. A formal RIA must follow the jurisdiction's guidance (e.g. US OMB Circular A-4, UK Better Regulation Framework) and use validated data — treat this as a rigorous first draft, not an official filing.
Required Inputs
Ask for these only if they aren't already provided:
- The proposed rule & problem — what's proposed and the market failure / risk / harm it addresses.
- Options — the realistic alternatives (including status quo / non-regulatory approaches), or ask the skill to develop them.
- Impacts & data — expected costs (compliance, admin, indirect) and benefits (safety, health, efficiency), who bears them, any figures available.
- Timeframe & discounting — the horizon and any required discount rate.
Output Format
Regulatory Impact Analysis: [rule]
1. Problem statement & rationale — the specific problem (market failure, externality, risk) and why intervention is needed now. If there's no clear problem, say so.
2. Objectives — what success looks like, in measurable terms.
3. Options considered — including the baseline (do nothing) and non-regulatory alternatives. Describe each.
4. Costs & benefits by option — for each option, the expected costs and benefits (quantified where possible; qualitative where not), over the timeframe. A comparison table:
| Option | Key costs | Key benefits | Net assessment |
|---|
State assumptions, data sources, and uncertainty honestly (ranges, sensitivity).
5. Distributional effects — who gains and who bears the costs (small business, regions, groups); any equity concerns.
6. Recommendation — the preferred option and why it's proportionate — the best net benefit for the burden imposed.
7. Implementation & review — enforcement, compliance burden, and how/when the rule's effect will be evaluated (sunset/review clause).
Show full SKILL.md (159 more words)Show less
Quality Checks
- The problem/market-failure is clearly established before any option is recommended
- Options include the do-nothing baseline and at least one non-regulatory or lighter alternative
- Costs and benefits are compared per option, quantified where data allows, with sources
- Uncertainty is stated honestly (ranges/sensitivity), not hidden behind point estimates
- Distributional effects and a proportionality-based recommendation are included
- A review/evaluation mechanism is specified
Anti-Patterns
- Do not assume regulation is the answer — establish the problem and test the baseline first
- Do not present only the preferred option — compare real alternatives
- Do not fabricate precise numbers — use ranges and label assumptions where data is thin
- Do not ignore who bears the cost — distributional/small-business impact matters
- Do not omit proportionality — the benefit must justify the burden imposed
Based On
Regulatory impact analysis practice (OMB Circular A-4 / Better Regulation): problem-first, options vs. baseline, cost-benefit, proportionality.
Example Trigger Phrases
- "Assess a regulation's impact."
- "Do a cost-benefit analysis of a policy?"
- "Justify a rulemaking."
- "Compare regulatory options."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/regulatory-impact-analysis of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Regulatory Impact Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Regulatory Impact Analysis this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1k | Automated safety check: Pass | MIT | |
| Cost Benefitbrycewang-stanford/Auto-Empirical-Research-Skills | 4.6k | — | ~11k | Automated safety check: Notes | Custom licence | |
| Cost Trackingaffaan-m/ECC | 277k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Cost Conversationruvnet/ruflo | 74k | — | ~407 | Automated safety check: Notes | MIT | |
| Cost Reportruvnet/ruflo | 74k | — | ~830 | Automated safety check: Notes | MIT | |
| Cost Optimizeruvnet/ruflo | 74k | — | ~997 | Automated safety check: Notes | MIT |
Similar skills
Cost Tracking
affaan-m/ECC
Track and report Claude Code token usage, spending, and budgets from the local ECC cost-tracker metrics log.
Cost Conversation
ruvnet/ruflo
Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost
Cost Report
ruvnet/ruflo
Generate a cost report showing token usage and USD costs by agent and model
Cost Optimize
ruvnet/ruflo
Analyze token usage patterns and recommend cost optimizations with estimated savings
Cost Track
ruvnet/ruflo
Auto-capture per-session token usage from the Claude Code session jsonl and persist to the cost-tracking namespace
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Regulatory Impact Analysis
What does Regulatory Impact Analysis do?
Produce a regulatory impact analysis (RIA) weighing the costs, benefits, and alternatives of a proposed rule. Regulatory Impact Analysis is an agent skill from mohitagw15856/pm-claude-skills. Produce a regulatory impact analysis (RIA) weighing the costs, benefits, and alternatives of a proposed rule.
When should I use Regulatory Impact Analysis?
Regulatory Impact Analysis fits situations like: asked to assess a regulations impact; do a cost-benefit analysis of a policy; justify a rulemaking; compare regulatory options.
How do I install Regulatory Impact Analysis in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill regulatory-impact-analysis -a claude-code`. Or copy the skill folder (skills/regulatory-impact-analysis in mohitagw15856/pm-claude-skills) into .claude/skills/regulatory-impact-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Regulatory Impact Analysis in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill regulatory-impact-analysis -a codex`. Or copy the skill folder (skills/regulatory-impact-analysis in mohitagw15856/pm-claude-skills) into .agents/skills/regulatory-impact-analysis in your project. Codex loads it when a task matches its description.
Can I use Regulatory Impact Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill regulatory-impact-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/regulatory-impact-analysis, .gemini/skills/regulatory-impact-analysis, .github/skills/regulatory-impact-analysis and .opencode/skills/regulatory-impact-analysis in your project.
What does Regulatory Impact Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Regulatory Impact Analysis is instructions for the agent only.
Does Regulatory Impact Analysis access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Regulatory Impact Analysis safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Regulatory Impact Analysis use?
Regulatory Impact Analysis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Regulatory Impact Analysis use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Regulatory Impact Analysis?
Skills that share tags, products or a category with Regulatory Impact Analysis: Cost Benefit (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars), Cost Tracking (affaan-m/ECC, 277k stars), Cost Conversation (ruvnet/ruflo, 74k stars) and Cost Report (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Regulatory Impact Analysis?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.