菜单
Transform technical findings into clear, structured written content: penetration test reports, vulnerability disclosures, security blog posts, and technical documentation.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/brucesongs/kali-claw --skill article-writing命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Semantic-layer attack testing against AI systems and LLM-integrated applications.
Cloud security covers security assessment for major cloud platforms including AWS, Azure, and GCP, with core focus on IAM misconfiguration detection, storage bucket exposure scanning, metadata service attacks, container escape, and Kubernetes RBAC auditing.
Defensive deception and honeypot deployment covering SSH/Telnet (Cowrie), web (OpenCanary), enterprise (HFish), ICS/SCADA (Conpot), all-in-one (T-Pot), AI-driven deception (Beelzebub), Thinkst Canarytokens (DNS, HTTP, file, AWS API key, SQL), Dionaea multi-protocol honeypot, notification pipelines (Slack/Teams webhooks), false positive tuning, and attacker engagement — including lure design, deployment OPSEC, IOC extraction, and attacker attribution.
基于 SOC 职业分类
正在显示 SKILL.md
| name | article-writing |
| description | Transform technical findings into clear, structured written content: penetration test reports, vulnerability disclosures, security blog posts, and technical documentation. |
| origin | openclaw |
| version | 0.2.0.2 |
| compatibility | ["openclaw","claude-code","cursor","windsurf"] |
| allowed-tools | ["Bash","Read","Write","Edit","WebSearch","WebFetch","Agent"] |
| defense_triple_required | false |
| metadata | {"domain":"knowledge","tool_count":0,"guide_count":8,"last_reviewed":"2026-07-26"} |
Article Writing skill domain covering knowledge operations.
Domain: knowledge
| Attribute | Value |
|---|---|
| Domain | Documentation & Communication |
| Skill ID | article-writing |
| Version | 1.0.0 |
| Hacker Laws | Law 8 (Learn from Every Operation), Law 11 (Share Knowledge, Build Legacy) |
| Related Skills | knowledge-ops, deep-research |
Transform technical findings into clear, structured written content: penetration test reports, vulnerability disclosures, security blog posts, and technical documentation.
Writing is the final step in the intelligence workflow — turning raw findings into actionable deliverables for clients, researchers, or the public.
| Type | Audience | Format | Length |
|---|---|---|---|
| Pentest Report | Client (technical + executive) | Executive Summary + Technical Findings | 10-50 pages |
| Vulnerability Disclosure | Vendor security team | CVE template + PoC | 2-5 pages |
| Security Blog Post | Public (technical) | Narrative + code samples | 1000-3000 words |
| Advisory | Public (mixed audience) | CVSS + mitigation steps | 500-1500 words |
| Technical Documentation | Internal team | How-to guide | Variable |
# Aggregate all findings from knowledge-ops
grep -rn "type: finding" memory/*target*.md | wc -l
# Extract high-confidence findings (>= 75)
grep -rn "confidence: [789][0-9]\|confidence: 100" memory/*target*.md -l | \
xargs grep -h "## Summary"
grep -rn memory/*target*.md
Follow the appropriate template (see below) for the article type. Outline before writing.
# Penetration Test Report: [Client Name]
**Date**: [date]
**Version**: [version]
**Prepared by**: [your org]
**Classification**: [Confidential/Restricted]
---
## Executive Summary
[Target]: [description of target scope]
[Duration]: [test dates]
[Findings Summary]: [count by severity]
### Key Findings
- **Critical**: [count] — [one-line impact]
- **High**: [count] — [one-line impact]
- **Medium**: [count] — [one-line impact]
- **Low**: [count] — [one-line impact]
### Business Impact
[2-3 sentences on overall risk to the organization]
### Recommendations Priority
1. [Most critical fix]
2. [Second priority]
3. [Third priority]
---
## Scope
**In Scope**:
- [systems/domains tested]
**Out of Scope**:
- [systems excluded]
**Testing Methodology**: [OWASP, PTES, custom]
---
## Findings
### Finding 1: [Vulnerability Name]
**Severity**: Critical
**CVSS**: 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
**Affected Systems**: [list]
##
## Description
[What is the vulnerability? How does it work?]
#### Evidence
```bash
[Commands used to discover/exploit]
[Screenshot or log output]
Short-term: [immediate fix] Long-term: [architectural improvement]
Verification: [how to verify fix]
[Continue for all findings]
| Date | Activity |
|---|---|
| [date] | Reconnaissance |
| [date] | Vulnerability scanning |
| [date] | Manual testing |
| [date] | Exploitation |
| [date] | Reporting |
### Vulnerability Disclosure Template
```markdown
# Vulnerability Disclosure: [Vulnerability Name]
**Date**: [discovery date]
**Severity**: [Critical/High/Medium/Low]
**CVSS**: [score] ([vector])
**CVE ID**: [if assigned, otherwise "Pending"]
---
## Affected Products
- **Product**: [name]
- **Versions**: [affected versions]
- **Fixed in**: [patched version, if known]
## Vulnerability Details
### Type
[SQL Injection / XSS / SSRF / etc.]
### Location
- **File**: [file path or URL]
- **Parameter**: [vulnerable parameter]
- **Method**: [GET/POST/etc.]
### Root Cause
[Technical explanation of why the vulnerability exists]
## Proof of Concept
```bash
[Minimal PoC to reproduce]
Expected Result: [what should happen] Actual Result: [what happens, demonstrating the vuln]
[Detailed impact analysis — what can an attacker achieve?]
[Code diff showing the fix, if simple]
[Temporary mitigation steps]
| Date | Event |
|---|---|
| [date] | Vulnerability discovered |
| [date] | Vendor notified |
| [date] | Vendor acknowledged |
| [date] | Patch released |
| [date] | Public disclosure |
[Your name/org]
### Security Blog Post Template
```markdown
# [Catchy Title]: [One-Sentence Hook]
**Published**: [date]
**Author**: [name]
**Tags**: [tag1, tag2, tag3]
---
## TL;DR
[2-3 sentences summarizing the entire post]
---
## Introduction
[Set the stage — why does this topic matter? What problem are you solving?]
## Background
[Context needed to understand the vulnerability/technique/tool]
## Discovery
[How did you find this? What were the initial signals?]
## Deep Dive
[Technical details — this is the meat of the post]
### Step 1: [Phase Name]
[Description]
```bash
[Commands]
[Output/screenshot]
[Continue for all steps]
[What can an attacker do with this? Real-world scenarios]
[Wrap up — key takeaways, call to action]
## Use Cases
1. **Pentest Deliverable**: Final report for client after engagement
2. **Responsible Disclosure**: Notify vendor of discovered vulnerability
3. **Knowledge Sharing**: Publish research findings publicly
4. **Internal Documentation**: Record methodology for team playbooks
5. **Advisory Publishing**: Warn community of active threat
## Writing Best Practices
- **Be precise**: Use exact file paths, line numbers, version numbers
- **Be reproducible**: Include all commands, payloads, and environment details
- **Be cautious**: Sanitize sensitive data (IPs, domains, real credentials)
- **Be visual**: Screenshots, diagrams, code blocks
- **Be actionable**: Every finding needs a clear fix
## Integration
- **Input**: knowledge-ops findings, test-cases validation results
- **Output**: Markdown/PDF reports, blog posts, advisories
- **Handoff**: Share with client, vendor, or publish publicly