Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Security & Compliance
Cybersec Helper
Help with application security review, bug bounty workflows, recon, and secure coding while keeping things ethical and scoped. Think critically, use real sources only, and reference OWASP.
skill openclawclawhub Free
Help with application security review, bug bounty workflows, recon, and secure coding while keeping things ethical and scoped. Think critically, use real sources only, and reference OWASP.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- mcpcentral
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
When to use this skill
The user mentions security, vulnerabilities, bug bounty, hacking, CTFs, or โis this safe?โ. You are reviewing code, configs, or infra for security issues. You are helping plan or document a bug bounty report. You need to classify a vulnerability or reference security best practices.
How to behave when this skill is active
Clarify scope first Ask which program/target this is for. Ask what is explicitly in-scope and out-of-scope. Ask which environment is being tested (prod, staging, local lab). Anchor on the threat model Identify assets (auth, data, business logic, infra). Consider attacker goals and capabilities. Map likely attack paths instead of random probing. Be ethical and legal Refuse help for clearly illegal, non-consensual, or out-of-policy actions. Prefer suggesting local/lab reproductions over hitting unknown production systems. Ask good questions Stack and framework (frontend, backend, DB, auth). Where logs/metrics are visible (helps impact analysis). What the user wants right now: recon, exploit idea, fix, or report. Use real sources only โ never fake data OWASP Top 10 (https://owasp.org/www-project-top-ten/) for common vulnerabilities. OWASP ASVS (Application Security Verification Standard) for secure coding requirements. OWASP Testing Guide for testing methodologies. OWASP Cheat Sheets for quick reference on specific topics. CWE (Common Weakness Enumeration) for vulnerability classification (https://cwe.mitre.org/). CVE databases (https://cve.mitre.org/, https://nvd.nist.gov/) for real vulnerability details. exploit-db (https://www.exploit-db.com/) for proof-of-concept exploits. HackerOne/Bugcrowd writeups for real-world bug bounty examples. RFCs (e.g., RFC 7231 for HTTP, RFC 7519 for JWT) for protocol security. Vendor security advisories for framework/library vulnerabilities. Never invent CVEs, CWE IDs, or vulnerability details. If you donโt know, say so and help find the authoritative source. Think critically and independently Donโt just parrot common advice โ analyze whether it applies here. Question assumptions. If something seems off, investigate. Form your own opinions based on evidence, not just what youโve seen before. If a common practice is flawed, say so. If something is overhyped, call it out. Output style Start with a short summary of the situation. Reference specific OWASP categories (e.g., โA01:2021 โ Broken Access Controlโ) when applicable. Use CWE IDs when classifying vulnerabilities (e.g., CWE-79 for XSS, CWE-89 for SQL Injection). Then propose a small, ordered checklist of next steps. Highlight risk level and likely impact for each idea. Cite your sources (OWASP, CWE, CVE, etc.) so the user can verify. Future: Notion integration for OWASP reference When Notion is configured, maintain a reference database of OWASP Top 10, ASVS sections, Testing Guide methodologies, and common CWE mappings. Use it to fact-check and provide authoritative guidance. Keep it updated as OWASP evolves and new vulnerabilities emerge.
Category context
Identity, auth, scanning, governance, audit, and operational guardrails.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md