SkillAgentSearch skills...

risky-changes

Verify assumptions before implementing large or risky changes to APIs, provider data, billing, pricing, quotas, or defaults

Install / Use

npx skills add davidondrej/skills --skill risky-changes

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Universal

Our assessment of risky-changes

risky-changes scores 82/100 on our quality scale, 352nd of 421 Education & Research skills we index.

Its SKILL.md is 2.8 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.

With 4,079 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so risky-changes is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

risky-changes compared with similar skills

All 4 of these similar skills score higher than risky-changes; compare them before choosing.

SkillScoreStarsUpdatedFormat
risky-changes (this skill)by davidondrej824.1k53d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
last30days-skillby mvanhorn10068.0ktodayCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install risky-changes?
Run npx skills add davidondrej/skills --skill risky-changes. The install tabs above show the steps for each supported agent.
Which AI agents does risky-changes work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is risky-changes safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is risky-changes still maintained?
The repository was last updated about 2 months ago, so risky-changes is actively maintained.

name: risky-changes description: 'Verify assumptions before implementing large or risky changes to APIs, provider data, billing, pricing, quotas, or defaults. Use when a mistake could affect customers or the user asks if a change is safe to ship. Checks real-world impact beyond passing tests.'

Risky Changes

A filter once passed every test but disabled ~99% of the feature on live data. Tests check code correctness; research and live measurement check whether a change is useful.

When this applies

Use for changes where being wrong is expensive or customer-visible:

  • Public API fields, filters, or response shaping
  • Dropping, transforming, or reordering upstream data
  • Billing, pricing, caps, or quotas
  • Defaults, thresholds, or provider request parameters
  • Unverified assumptions about external data or user behavior

If unsure whether a change qualifies, apply this process.

1. Identify assumptions

List the assumptions the change depends on. Mark which have evidence and which are still unverified.

2. Research before implementing

Use available research tools and reliable sources. Investigate each distinct question separately, covering at least:

  • How do leading products handle this design decision?
  • What does real-world data look like: frequencies, shapes, and edge cases?
  • What do users or agents actually need?

If evidence contradicts an assumption, reconsider the design before coding. If research is unavailable or inconclusive, state the gap; do not treat the assumption as verified. Do not ship while material assumptions remain unverified.

3. Measure real behavior

Run 10–20+ realistic cases against the real endpoint or provider:

  • Base cases on real usage; vary topics, parameters, languages, and edge conditions.
  • Define benchmarks per case: speed, quality, accuracy, and how often the new behavior occurs.
  • Use hard numbers where possible. For subjective quality, use blind, criteria-based judging.
  • Compare before and after when both can be measured.
  • Read-only production analysis also counts as measurement.

Save the cases and results in the project's evals folder, e.g. docs/evals/YYYY-MM-DD-<endpoint>-<focus>.md. Create the folder if needed. Without this record, the change is not verified. Unit tests do not replace live measurement.

4. Confirm product-owner approval before shipping

Present decisions that affect what customers see or pay, with supporting research and measurements. Get the product owner's approval for those decisions; do not bury them in a plan or code default. Existing approval counts if it covers the actual behavior being shipped.

5. Verify after deployment

Within one day, measure the change on real traffic through read-only production analysis or a live sweep. Report results that differ from expectations immediately.

Related Skills

View on GitHub
GitHub Stars4.1k
CategoryEducation
Updated1mo ago
Forks601

Languages

Shell

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions