SKILL·68FA44

mkdocs-danger

vamseeachanta
Updated 2 months ago
86 views
3
2
3
View on GitHub
Othergeneral

About

The mkdocs-danger skill creates critical warning callouts in documentation that highlight actions potentially causing data loss or security issues. It's specifically designed for emphasizing high-risk operations within mkdocs-generated documentation. Use this skill when you need to prominently warn developers about dangerous or irreversible actions.

Quick Install

Claude Code

Recommended
Primary
npx skills add vamseeachanta/workspace-hub -a claude-code
Plugin CommandAlternative
/plugin add https://github.com/vamseeachanta/workspace-hub
Git CloneAlternative
git clone https://github.com/vamseeachanta/workspace-hub.git ~/.claude/skills/mkdocs-danger

Copy and paste this command in Claude Code to install this skill

GitHub Repository

vamseeachanta/workspace-hub
Path: .claude/skills/_internal/documentation/mkdocs/danger
0
FAQ

Frequently asked questions

What is the mkdocs-danger skill?

mkdocs-danger is a Claude Skill by vamseeachanta. Skills package instructions and resources that Claude loads on demand, so Claude can perform mkdocs-danger-related tasks without extra prompting.

How do I install mkdocs-danger?

Use the install commands on this page: add mkdocs-danger to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does mkdocs-danger belong to?

mkdocs-danger is in the Other category.

Is mkdocs-danger free to use?

Yes. mkdocs-danger is listed on AIMCP and free to install.

Related Skills

legal-sanity-review
Other

This mandatory workflow scans code for legal risks like client names or proprietary references before cross-review. It blocks the review cycle if violations are found, requiring fixes first. Use it as a pre-gate for PR creation, code porting, or any cross-review trigger.

View skill
brainstorming
Other

The brainstorming skill transforms initial ideas into detailed specifications through iterative questioning and collaborative dialogue. It helps developers explore design options, evaluate trade-offs, and create shared understanding before implementation. This prevents rework by systematically refining concepts into actionable plans.

View skill
repo-cleanup-structure-section-updates
Other

This skill handles repository structure documentation updates after cleanup operations. It automatically updates directory trees, removes references to deleted folders, and documents architectural changes like `.claude/` folders and consolidated scripts. Use it to maintain accurate structure sections in README files following repository reorganization.

View skill
repo-cleanup-references-to-remove
Other

This skill identifies legacy directories and files that should be removed or consolidated during repository cleanup. It provides a specific checklist for developers, including paths like `.agent-os/` and `.drcode/` that are obsolete or have been moved to new locations. Use this reference when cleaning up a Claude Code project to ensure proper migration and deletion of outdated assets.

View skill