ReddRadar
Topic: claude
14,433 skills in this topic.
-
Red Team Tools and Methodology
This skill should be used when the user asks to "follow red team methodology", "perform bug bounty hunting", "automate reconnaissance", "hunt for XSS vulnerabilities", "enumerate subdomains", or needs security researcher techniques and tool configurations from top bug bounty hunters.
zebbern/claude-code-guide 3,752
-
Security Scanning Tools
This skill should be used when the user asks to "perform vulnerability scanning", "scan networks for open ports", "assess web application security", "scan wireless networks", "detect malware", "check cloud security", or "evaluate system compliance". It provides comprehensive guidance on security scanning tools and methodologies.
zebbern/claude-code-guide 3,752
-
Shodan Reconnaissance and Pentesting
This skill should be used when the user asks to "search for exposed devices on the internet," "perform Shodan reconnaissance," "find vulnerable services using Shodan," "scan IP ranges with Shodan," or "discover IoT devices and open ports." It provides comprehensive guidance for using Shodan's search engine, CLI, and API for penetration testing reconnaissance.
zebbern/claude-code-guide 3,752
-
SMTP Penetration Testing
This skill should be used when the user asks to "perform SMTP penetration testing", "enumerate email users", "test for open mail relays", "grab SMTP banners", "brute force email credentials", or "assess mail server security". It provides comprehensive techniques for testing SMTP server security.
zebbern/claude-code-guide 3,752
-
SQL Injection Testing
This skill should be used when the user asks to "test for SQL injection vulnerabilities", "perform SQLi attacks", "bypass authentication using SQL injection", "extract database information through injection", "detect SQL injection flaws", or "exploit database query vulnerabilities". It provides comprehensive techniques for identifying, exploiting, and understanding SQL injection attack vectors across different database systems.
zebbern/claude-code-guide 3,752
-
SQLMap Database Penetration Testing
This skill should be used when the user asks to "automate SQL injection testing," "enumerate database structure," "extract database credentials using sqlmap," "dump tables and columns from a vulnerable database," or "perform automated database penetration testing." It provides comprehensive guidance for using SQLMap to detect and exploit SQL injection vulnerabilities.
zebbern/claude-code-guide 3,752
-
SSH Penetration Testing
This skill should be used when the user asks to "pentest SSH services", "enumerate SSH configurations", "brute force SSH credentials", "exploit SSH vulnerabilities", "perform SSH tunneling", or "audit SSH security". It provides comprehensive SSH penetration testing methodologies and techniques.
zebbern/claude-code-guide 3,752
-
Top 100 Web Vulnerabilities Reference
This skill should be used when the user asks to "identify web application vulnerabilities", "explain common security flaws", "understand vulnerability categories", "learn about injection attacks", "review access control weaknesses", "analyze API security issues", "assess security misconfigurations", "understand client-side vulnerabilities", "examine mobile and IoT security flaws", or "reference the OWASP-aligned vulnerability taxonomy". Use this skill to provide comprehensive vulnerability definitions, root causes, impacts, and mitigation strategies across all major web security categories.
zebbern/claude-code-guide 3,752
-
Windows Privilege Escalation
This skill should be used when the user asks to "escalate privileges on Windows," "find Windows privesc vectors," "enumerate Windows for privilege escalation," "exploit Windows misconfigurations," or "perform post-exploitation privilege escalation." It provides comprehensive guidance for discovering and exploiting privilege escalation vulnerabilities in Windows environments.
zebbern/claude-code-guide 3,752
-
Wireshark Network Traffic Analysis
This skill should be used when the user asks to "analyze network traffic with Wireshark", "capture packets for troubleshooting", "filter PCAP files", "follow TCP/UDP streams", "detect network anomalies", "investigate suspicious traffic", or "perform protocol analysis". It provides comprehensive techniques for network packet capture, filtering, and analysis using Wireshark.
zebbern/claude-code-guide 3,752
-
WordPress Penetration Testing
This skill should be used when the user asks to "pentest WordPress sites", "scan WordPress for vulnerabilities", "enumerate WordPress users, themes, or plugins", "exploit WordPress vulnerabilities", or "use WPScan". It provides comprehensive WordPress security assessment methodologies.
zebbern/claude-code-guide 3,752
-
Cross-Site Scripting and HTML Injection Testing
This skill should be used when the user asks to "test for XSS vulnerabilities", "perform cross-site scripting attacks", "identify HTML injection flaws", "exploit client-side injection vulnerabilities", "steal cookies via XSS", or "bypass content security policies". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.
zebbern/claude-code-guide 3,752
-
_template_reference_first
Internal template for creating or refactoring a skill into the repository's reference-first shape.
**Trigger**: reference-first template, blueprint skill, create a reusable skill, refactor a script-heavy skill.
**Use when**: you need a lean `SKILL.md`, explicit `references/`, machine-readable `assets/`, and a minimal deterministic `run.py`.
**Skip if**: the task is a one-off workflow that will not be reused as a skill.
**Network**: none.
**Guardrail**: keep domain knowledge and writing exemplars out of `run.py`; make reference loading explicit; do not ship reader-facing placeholder text.
WILLOSCAR/research-units-pipeline-skills 377
-
agent-survey-corpus
Download a small corpus of open-access arXiv survey/review PDFs about LLM agents and extract text for style learning.
**Trigger**: agent survey corpus, ref corpus, download surveys, 学习综述写法, 下载 survey.
**Use when**: you want to study how real agent surveys structure sections (6–8 H2), size subsections, and write evidence-backed comparisons.
**Skip if**: you cannot download PDFs (no network) or you don't want local PDF files.
**Network**: required.
**Guardrail**: only download arXiv PDFs; store under `ref/` and keep large files out of git.
WILLOSCAR/research-units-pipeline-skills 377
-
anchor-sheet
Extract per-subsection “anchor facts” (NO PROSE) from evidence packs so the writer is forced to include concrete numbers/benchmarks/limitations instead of generic summaries.
**Trigger**: anchor sheet, anchor facts, numeric anchors, evidence hooks, 写作锚点, 数字锚点, 证据钩子.
**Use when**: `outline/evidence_drafts.jsonl` exists and you want stronger, evidence-anchored writing in `sections/*.md`.
**Skip if**: evidence packs are incomplete (fix `evidence-draft` first).
**Network**: none.
**Guardrail**: NO PROSE; do not invent facts; only select from existing evidence snippets/highlights.
WILLOSCAR/research-units-pipeline-skills 377
-
appendix-table-writer
Curate reader-facing survey tables for the Appendix (clean layout + high information density), using only in-scope evidence and existing citation keys.
**Trigger**: appendix tables, publishable tables, survey tables, reader tables, 附录表格, 可发表表格, 综述表格.
**Use when**: you have C4 artifacts (evidence packs + anchor sheet + citations) and want tables that look like a real survey (not internal logs).
**Skip if**: `outline/tables_appendix.md` already exists and is refined (>=2 tables; citation-backed; no placeholders; not index-y).
**Network**: none.
**Guardrail**: no invented facts; no pipeline jargon; no paragraph cells; use only keys present in `citations/ref.bib`.
WILLOSCAR/research-units-pipeline-skills 377
-
argument-selfloop
Argument self-loop: maintain an argument ledger + premise consistency report for drafted sections.
**Trigger**: argument self-loop, argument chain, premise consistency, section self-check, paragraph contract, 论证自循环, 论证链路, 前提一致性, 段落论证动作.
**Use when**: you are in C5 (PROSE allowed), `sections/*.md` exist, and you want to prevent “smooth but hollow” writing by enforcing argument moves + premise hygiene before merge.
**Skip if**: you are pre-C2 (NO PROSE), or evidence packs are scaffolded/thin (route upstream to `evidence-selfloop` first).
**Network**: none.
**Guardrail**: do not invent facts; do not add/remove/move citation keys; do not move citations across subsections; the argument ledger is an intermediate artifact and must never be inserted into the paper.
WILLOSCAR/research-units-pipeline-skills 377
-
artifact-contract-auditor
Audit the workspace against the pipeline artifact contract (DONE outputs + pipeline target_artifacts).
Writes `output/CONTRACT_REPORT.md`.
**Trigger**: contract audit, artifact contract, missing artifacts, target_artifacts, CONTRACT_REPORT.
**Use when**: you want an auditable PASS/FAIL view of whether a workspace is complete and self-contained (end of run or before sharing).
**Skip if**: you are still intentionally mid-run and don’t care about completeness yet (but it’s still useful as a snapshot).
**Network**: none.
**Guardrail**: analysis-only; do not edit content artifacts; only write the report.
WILLOSCAR/research-units-pipeline-skills 377
-
arxiv-search
Retrieve paper metadata from arXiv using keyword queries and save results as JSONL (`papers/papers_raw.jsonl`).
**Trigger**: arXiv, arxiv, paper search, metadata retrieval, 文献检索, 论文检索, 拉取元数据, 离线导入.
**Use when**: 需要一个初始论文集合（survey/snapshot 的 Stage C1），来源为 arXiv（在线检索或离线导入 export）。
**Skip if**: 已经有可用的 `papers/papers_raw.jsonl`，或数据源不是 arXiv。
**Network**: 在线检索需要网络；离线 `--input <export.*>` 不需要网络。
**Guardrail**: 只做 metadata；不要在 `output/` 写长 prose。
WILLOSCAR/research-units-pipeline-skills 377
-
bias-assessor
Add bias/risk-of-bias assessment fields to an extraction table and populate them consistently.
**Trigger**: bias, risk-of-bias, RoB, evidence quality, 偏倚评估, 证据质量.
**Use when**: systematic review 已生成 `papers/extraction_table.csv`，需要在 synthesis 前补齐偏倚/质量字段。
**Skip if**: 不是 systematic review，或还没有 `papers/extraction_table.csv`。
**Network**: none.
**Guardrail**: 使用简单可复核刻度（low/unclear/high）+ 简短 notes；保持字段一致性。
WILLOSCAR/research-units-pipeline-skills 377
-
chapter-briefs
Build per-chapter (H2) writing briefs (NO PROSE) so the final survey reads like a paper (chapter leads + cross-H3 coherence) without inflating the ToC.
**Trigger**: chapter briefs, H2 briefs, chapter lead plan, section intent, 章节意图, 章节导读, H2 卡片.
**Use when**: `outline/outline.yml` + `outline/subsection_briefs.jsonl` exist and you want thicker chapters (fewer headings, more logic).
**Skip if**: the outline is still changing heavily (fix outline/mapping first).
**Network**: none.
**Guardrail**: NO PROSE; do not invent papers; only reference subsection ids and already-mapped papers.
WILLOSCAR/research-units-pipeline-skills 377
-
chapter-lead-writer
Write H2 chapter lead blocks (`sections/S<sec_id>_lead.md`) that preview the chapter's comparison lens and connect its H3 subsections, without adding new facts.
**Trigger**: chapter lead writer, section lead writer, H2 lead, lead paragraph, 章节导读, 章节导语.
**Use when**: you have H2 chapters with multiple H3 subsections and the draft reads like paragraph islands across subsections.
**Skip if**: the outline has no H3 subsections, or `outline/chapter_briefs.jsonl` is missing.
**Network**: none.
**Guardrail**: no new facts/citations; no headings; no narration templates; use only citation keys present in `citations/ref.bib`.
WILLOSCAR/research-units-pipeline-skills 377
-
chapter-skeleton
Build a retrieval-informed chapter skeleton (`outline/chapter_skeleton.yml`) from taxonomy/core scope before stable H3 decomposition.
**Trigger**: chapter skeleton, chapter-level outline, H2 skeleton, section-first survey, 章节骨架, 章级骨架.
**Use when**: survey structure should stabilize chapter-level intent before subsection mapping and writing cards.
**Skip if**: `outline/chapter_skeleton.yml` already exists and is refined.
**Network**: none.
**Guardrail**: NO PROSE; do not invent papers; keep output chapter-level only.
WILLOSCAR/research-units-pipeline-skills 377
-
citation-anchoring
Regression-check citation anchoring (citations stay in the same subsection) to prevent “polish drift” that breaks claim→evidence alignment.
**Trigger**: citation anchoring, citation drift, regression, cite stability, 引用锚定, 引用漂移.
**Use when**: after editing/polishing, you want to confirm citations did not migrate across `###` subsections.
**Skip if**: you do not have a baseline anchor file yet.
**Network**: none.
**Guardrail**: analysis-only; do not edit content.
WILLOSCAR/research-units-pipeline-skills 377