add-community-skill

name	add-community-skill
description	Adding a Community Agent Skill: a Markdown attack-workflow file that users import from the catalog, which then competes in the Intent Router and is injected into the agent's system prompt. No Python, no rebuild - but it must name only real tools and stay classifiable. Trigger: adding or editing a .md workflow under agentic/community-skills/; authoring an importable attack skill (not a hardcoded one); editing the community-skills catalog or its README.
license	MIT
metadata	{"author":"redamon","version":"1.0.0","scope":["agentic"],"auto_invoke":["Adding a Community Agent Skill (importable .md attack workflow)"]}

When to Use

• Shipping a battle-tested attack workflow as an importable .md, without hardcoding it into Python.

For a hardcoded, first-class skill (9-layer wiring, badge, per-project toggle), use builtin-agent-skill instead. For a reference/theory doc rather than a workflow, that is a Community Chat Skill (different flow).

---

Critical Rules

• NEVER invent tool names. Every step must name a tool the agent actually has: query_graph, kali_shell, execute_curl, execute_code, execute_playwright, execute_nuclei, execute_hydra, metasploit_console. A step naming a non-existent tool is dead on arrival.