writing-offensive-skills

仓库创建 2026年5月19日最近提交 24 天前SkillHot 收录 21 天前
▸ 精选理由

对贡献者与审稿人必读,保证技能一致性与可运行性

这个 Skill 做什么

提供本仓库中编写/编辑 offensive-skills 的规范、模板与要求

给在仓库里编写或修改 offensive-skills 的人一套规范和模板,包括 SKILL.md 字段、触发说明、技术地图、可运行脚本、OPSEC/检测注意事项和红旗表格等。新增技能、更新说明或准备可执行示例时会用到。特点是沿用 superpowers 的约定并强调测试驱动,使技能易被发现、验证并规范记录,方便团队协作与审计。

▸ 展开 SKILL.md 英文原文

Use when creating or editing a skill in this offensive-claude repo — for the SKILL.md conventions (trigger descriptions, technique map, runnable scripts, OPSEC/detection, red-flags tables, flowchart rules)

Skill 开发管理技能规范文档红队通用
326
Stars
58
Forks
37
仓库内 Skill
+15
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/hypnguyen1209/offensive-claude/main/skills/writing-offensive-skills/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/hypnguyen1209/offensive-claude/main/skills/writing-offensive-skills/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# Writing Offensive Skills

## Overview

Conventions for authoring skills in this repo so the dispatcher can find them and operators can
trust them. This adapts superpowers' skill conventions to offensive security.

**REQUIRED BACKGROUND:** superpowers:writing-skills (the general conventions) and
superpowers:test-driven-development (skills are tested like code — baseline failure first).

## Description = triggers only

The `description:` field decides whether the dispatcher loads the skill. Write **`Use when…`**
triggering conditions and symptoms ONLY — never summarize the skill's workflow (a workflow summary
makes Claude follow the description instead of reading the skill).

```yaml
# BAD  
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有