How do I install the Skill Library Cleaner Risk Block skill?

Run npx skillmds@latest add aisflows/skill-library-cleaner-risk-block in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Skill Library Cleaner Risk Block safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Skill Library Cleaner Risk Block?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Skill Library Cleaner Risk Block free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Skill Library Cleaner Risk Block?

aisflows (@aisflows) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Skill Library Cleaner Risk Block by aisflows

Name: Skill Library Cleaner Risk Block
Author: aisflows

Skill Library Cleaner Risk Block

Use as step 2 of AIS FLOWS Skill Library Cleaner to separate risky AI-agent skill/source items before cleanup, producing RISK_BLOCKLIST.md and RISK_BLOCKLIST.json with install/runtime/API/credential/browser/package-script blockers.

aisflows d2d6a8b 2.2 KB Updated Sep 17, 2026

File contents

Skill Library Cleaner / Risk Block

Role

Separate items that must not enter the active clean library yet.

Input:

machine/INVENTORY.json

Output:

reports/RISK_BLOCKLIST.md
machine/RISK_BLOCKLIST.json

Block Signals

Block or quarantine from active shelf when an item includes:

installer commands;
npx, npm install, pip install, shell-pipe installers;
package scripts or hooks;
unknown binaries;
browser profile/cookie workflows;
token/keyring/credential/.env references;
provider/API/billing flows;
unclear license/source inheritance;
destructive filesystem instructions.

Risk routing is not a malware accusation. It is a release-control decision: the cleaner keeps high-impact skills out of the active shelf until a human explicitly approves them.

Decisions

Allowed risk decisions:

active-eligible
blocked-risk
reference-only
needs-human-review
license-review

Routing Matrix

signal	default route	note
install command, package script, binary, shell-pipe installer	`blocked-risk`	never active by default
secrets, cookies, browser profile, keyring, token handling	`blocked-risk`	do not inspect secret material
provider/API/billing/key setup	`needs-human-review` or `blocked-risk`	block when it asks to run/setup; review when it only documents safe usage
browser/live-app/workstation control	`needs-human-review`	may be safe but needs scope approval
unclear source/license	`license-review`	keep out of publishable package
useful but too broad/noisy	`reference-only`	preserve value without making it active

Required Fields

For every non-active item include:

risk route;
severity: low, medium, high, or critical;
concrete evidence;
why it cannot be active now;
what approval or rewrite would clear it.

Pass Condition

No risky item can become canonical or active before a separate review clears it.

---name: skill-library-cleaner-risk-blockdescription: Use as step 2 of AIS FLOWS Skill Library Cleaner to separate risky AI-agent skill/source items before cleanup, producing RISK_BLOCKLIST.md and RISK_BLOCKLIST.json with install/runtime/API/credential/browser/package-script blockers.---# Skill Library Cleaner / Risk Block## RoleSeparate items that must not enter the active clean library yet.Input:```textmachine/INVENTORY.json```Output:```textreports/RISK_BLOCKLIST.mdmachine/RISK_BLOCKLIST.json```## Block SignalsBlock or quarantine from active shelf when an item includes:- installer commands;- `npx`, `npm install`, `pip install`, shell-pipe installers;- package scripts or hooks;- unknown binaries;- browser profile/cookie workflows;- token/keyring/credential/.env references;- provider/API/billing flows;- unclear license/source inheritance;- destructive filesystem instructions.Risk routing is not a malware accusation. It is a release-control decision: the cleaner keeps high-impact skills out of the active shelf until a human explicitly approves them.## DecisionsAllowed risk decisions:- `active-eligible`- `blocked-risk`- `reference-only`- `needs-human-review`- `license-review`## Routing Matrix| signal | default route | note ||---|---|---|| install command, package script, binary, shell-pipe installer | `blocked-risk` | never active by default || secrets, cookies, browser profile, keyring, token handling | `blocked-risk` | do not inspect secret material || provider/API/billing/key setup | `needs-human-review` or `blocked-risk` | block when it asks to run/setup; review when it only documents safe usage || browser/live-app/workstation control | `needs-human-review` | may be safe but needs scope approval || unclear source/license | `license-review` | keep out of publishable package || useful but too broad/noisy | `reference-only` | preserve value without making it active |## Required FieldsFor every non-active item include:- risk route;- severity: `low`, `medium`, `high`, or `critical`;- concrete evidence;- why it cannot be active now;- what approval or rewrite would clear it.## Pass ConditionNo risky item can become canonical or active before a separate review clears it.

Frequently asked questions