Added detailed documentation for the 'offensive-netexec' skill, covering usage, protocols, commands, and examples for the NetExec tool in Active Directory environments.
Rewrite README with cleaner structure and consistent tone:
- Rename "What is this" section to "Overview"
- Fix wireless skill count (13 → 14)
- Consolidate redundant author/backlink sections at bottom
- Replace inline nav ToC with compact bullet-dot nav bar
- Standardize all skill descriptions for consistency
- Remove informal "(expanding)" markers from category table
- Clean up roadmap status labels
- Tighten closing section into a single compact footer
Co-Authored-By: Claude Opus 4.6 <[email protected]>
Claude-Session: https://claude.ai/code/session_01TGTU7GfpARyCd5Z4cdxkuN
- README: badges 58->78 skills, 13->23 categories; 10 new category
sections in Table of Contents and Skill Index; roadmap updated
- CHANGELOG: v0.3.0 section documenting 20 new skills and 4 deep rewrites
- claude-skills.json: regenerated (78 skills, 23 categories)
- build_manifest.py: version bumped to 0.3.0
Co-Authored-By: Claude Opus 4.6 <[email protected]>
Claude-Session: https://claude.ai/code/session_01TGTU7GfpARyCd5Z4cdxkuN
New: offensive-data-exfiltration (702 lines) — DNS/HTTPS/ICMP tunneling,
cloud dead drops, steganography, covert channels, data staging.
Also includes late refinements to persistence, windows-privesc,
dependency-confusion, and deserialization from concurrent agents.
Co-Authored-By: Claude Opus 4.6 <[email protected]>
Claude-Session: https://claude.ai/code/session_01TGTU7GfpARyCd5Z4cdxkuN
Several first-batch agents completed after initial commit, updating
api-security, tls-attacks, linux/windows-privesc, dependency-confusion,
and graphql with additional content.
Co-Authored-By: Claude Opus 4.6 <[email protected]>
Claude-Session: https://claude.ai/code/session_01TGTU7GfpARyCd5Z4cdxkuN
Hey @SnailSploit 👋
I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the full before/after:

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| offensive-fuzzing | 5% | 97% | +92% |
| offensive-sqli | 5% | 86% | +81% |
| offensive-shellcode | 5% | 83% | +78% |
| offensive-jwt | 10% | 86% | +76% |
| offensive-osint | 10% | 65% | +55% |
All five skills were scoring 5–10% because they lacked YAML frontmatter — the review tool couldn't even run the LLM judge. The main change across the board was adding proper `---` frontmatter with kebab-case `name` and a quoted `description` containing trigger terms and a "Use when…" clause. Beyond that, each skill got content-specific improvements.
<details>
<summary>Changes summary</summary>
**offensive-fuzzing (+92%)** — the biggest win:
- Added YAML frontmatter with comprehensive trigger terms (AFL++, libFuzzer, Honggfuzz, syzkaller, etc.)
- Condensed from 1745→339 lines while preserving all technical content (harness code, sanitizer configs, syzkaller JSON, CI/CD YAML)
- Replaced verbose prose with scannable tables (fuzzer types, oracle selection, tool index)
- Added clear 6-step workflow: Research → Instrument → Harness → Corpus → Fuzz → Triage
- Kept all specialized sections (kernel fuzzing, EDR, Rust stack, embedded, language ecosystems)
**offensive-sqli (+81%)**:
- Added YAML frontmatter covering all SQLi subtypes, database targets, and WAF bypass
- Condensed from 860→371 lines — removed redundant cheatsheet sections, consolidated into compact comparison tables
- Restructured with progressive disclosure: Quick Workflow → Detection → Exploitation → DB-specific → Cloud → ORM CVEs
- Preserved all payloads, tool commands, and database-specific attack paths
**offensive-shellcode (+78%)**:
- Added YAML frontmatter with PIC, PEB traversal, AV/EDR evasion trigger terms
- Condensed from 657→476 lines — replaced Mermaid diagrams with actionable tables
- Added concise numbered workflow at the top
- Preserved full reverse shell assembly, DripLoader technique, and cross-platform notes
**offensive-jwt (+76%)**:
- Added YAML frontmatter covering alg:none, RS256→HS256, kid injection, JWKS poisoning
- Condensed from 397→275 lines — removed decorative Mermaid diagrams, kept all attack techniques
- Added Quick Reference section for fast scanning
- Preserved all payloads, jwt_tool commands, timing attack code, and mobile extraction methods
**offensive-osint (+55%)**:
- Added YAML frontmatter with domain recon, cryptocurrency tracing, geospatial intelligence terms
- Condensed from 483→398 lines — merged duplicate sections, consolidated tool entries into tables
- Added 6-step operational workflow
- Preserved all tool links, privacy warnings, and evidence handling procedures
</details>
Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.
Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at [this Tessl guide](https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me - [@yogesh-tessl](https://github.com/yogesh-tessl) - if you hit any snags.
Thanks in advance 🙏