article-writing

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

Summary

Article Writing skill domain covering knowledge operations.

Domain: knowledge

Skill Identity

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

Purpose

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.

Article Types

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

Methodology

Phase 1: Gather Intelligence

# 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