75 matching cards · showing 1–20 · page 1 of 4
Bootstrap file for AI agents only; human readers are redirected to README.md. Contains the execute-immediately first instruction, the platform deployment routing table, an example report format, dependency tables, and quick-start paths for wiring any code CLI into the router.
Root-level Kali Linux shortcut entry. Defers to kali/README-kali.md as the source of truth; gives an AI read-then-execute path and a 30-second human quick start, and explains this file's relationship to the main package.
Chinese-language project overview and the most detailed human documentation in the repo. Mirrors README.md (about, quick start, installation, usage, supported scenarios, key files, repository layout) with fuller explanations. Primary reference for Chinese-speaking users.
Human-facing project overview and quick start for reverse-skill, a cybersecurity skills router. Covers About, Built With, Getting Started (prerequisites, installation), Usage with supported scenarios, key files, repository layout and license. The entry point for human contributors.
Chinese edition of the routing matrix (by target type, by user intent, route-not-matched handling, cross-module path crossing). Same enforced protocol: complete routing before acting, output the routing rationale, and pass case-init/scope.md before ACT on a target.
Full task-to-skill routing matrix. Routes by target type, user intent and toolchain; includes CTF wording normalization, ambiguous-intent recovery, route-not-matched handling and cross-module path crossing. Enforced, not advisory: routing must complete before execution.
PRIMARY fast-path routing ladder, kept in sync with scripts/master-route.ps1. Defines the route-before-acting execution contract, the priority order, the scope gate before ACT, evidence append and the reading order. The first file an agent consults.
Master controller and entry point for the skills tree. YAML frontmatter declares the routing scope; the body defines the routing execution contract, RFC-2119 instruction levels, the unified entry, the next-step menu pattern, the precedent library and auto-evolution.
Chinese edition of RULES.md: the same authorization gates and canonical behavior chain (trigger keywords, routing entry, execution principles, security boundaries, completion checklist). The largest file in the navigation set; it drives routing for Chinese-language prompts.
The single source of truth for the behavior chain and authorization gates. Defines the execute-immediately mandate, global config injection on first use, bilingual trigger keywords, the routing entry, execution principles, the canonical behavior chain and a completion checklist.
Root-level file that Claude Code auto-loads. Declares the repository a task skill router for authorized reverse engineering and security work, names RULES.md as the single source of truth, and fixes the routing order, with per-OS first-run setup and a coherence check.
Guide for adding a new skill module to the pack. Defines the standard flow: compliance-engineering constraints, when to add a skill, the directory-structure template, and the mandatory SKILL.md contents including the strong-execution skeleton that forces agents to act rather than merely acknowledge.
Keep a Changelog / SemVer changelog. Documents the 1.0.0 release (2026-07-18): the ops/combat-contract layer, PRIMARY routing and case tooling, core skills and localization, plus an Unreleased section with Fixed, Security, Added and Removed changes.
Navigation across the markdown files of zhaoxuya520/reverse-skill with measured metrics: 402 .md files, 83 SKILL.md, all in git mode 100644. Documentation is split by audience — 46 KB for humans, 157 KB for agents. Covers the routing chain and three license zones (MIT / GPL-3.0 / third-party MIT).
Cookbook-style walkthrough for cryptographically signed receipts on every Claude Code tool call. This is the teaching skill. For the runtime implementation, install the protect-mcp plugin. Use it to give an agent explicit responsibilities, steps and constraints.
You are a Senior Code Reviewer with 30 years of experience in software quality, security analysis, and architectural compliance. You are objective, constructive, and precise. You explain the why behind every finding. Use it to give an agent explicit responsibilities, steps and constraints.
Threat-mitigation mapping — templates and worked examples captures reusable agent playbook guidance for application security & threat modeling. Use it to give an agent explicit responsibilities, steps and constraints.
User] -- [Web App] -- [API Gateway] -- [Backend Services] | v [Database]. Use it to give an agent explicit responsibilities, steps and constraints.
security-requirement-extraction — templates and worked examples captures reusable agent playbook guidance for application security & threat modeling. Use it to give an agent explicit responsibilities, steps and constraints.
attack-tree-construction — templates and worked examples captures reusable agent playbook guidance for application security & threat modeling. Use it to give an agent explicit responsibilities, steps and constraints.