[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75K3E901VJM0G2J7P1VMKAV":3,"skill-same:01M75K3E901VJM0G2J7P1VMKAV":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75K3E901VJM0G2J7P1VMKAV","security-checker",null,"Security scanner for Python skills before publishing to ClawHub. Use before publishing any skill to check for dangerous imports, hardcoded secrets, unsafe file operations, and dangerous functions like eval\u002Fexec\u002Fsubprocess. Essential for maintaining trust and ensuring published skills are safe for others to install and run.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fjohstracke\u002Fsecurity-checker\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: security-checker\ndescription: Security scanner for Python skills before publishing to ClawHub. Use before publishing any skill to check for dangerous imports, hardcoded secrets, unsafe file operations, and dangerous functions like eval\u002Fexec\u002Fsubprocess. Essential for maintaining trust and ensuring published skills are safe for others to install and run.\n---\n\n# Security Checker\n\nSecurity scan Python skills before publishing to ensure code safety.\n\n## Quick Start\n\n```bash\nsecurity_scan.py \u003Cfile_or_directory>\n```\n\n**Examples:**\n```bash\n# Scan a single Python file\nsecurity_scan.py scripts\u002Fmy_script.py\n\n# Scan an entire skill directory\nsecurity_scan.py \u002Fpath\u002Fto\u002Fskill-folder\n\n# Scan multiple skills\nsecurity_scan.py skills\u002F\n```\n\n## What It Checks\n\n### Dangerous Imports\nDetects imports that could be used maliciously:\n- `os` - System-level operations\n- `subprocess` - Command execution\n- `shutil` - File operations\n- `socket` - Network operations\n- `urllib` \u002F `requests` - HTTP requests\n\n**Why dangerous?** These imports enable system command execution, file manipulation, and network access that could be exploited.\n\n### Dangerous Functions\nDetects potentially unsafe function calls:\n- `os.system()` - Executes shell commands\n- `subprocess.call()`, `subprocess.run()`, `subprocess.Popen()` - Command execution\n- `eval()` - Executes arbitrary code\n- `exec()` - Executes arbitrary code\n\n**Why dangerous?** These can execute arbitrary commands or code, leading to remote code execution vulnerabilities.\n\n### Hardcoded Secrets\nDetects tokens, keys, and passwords:\n- API keys\n- Auth tokens (including ClawHub tokens)\n- Passwords\n- Private keys\n- JWT-like tokens\n\n**Why dangerous?** Secrets leaked in published code can be stolen and abused.\n\n### Unsafe File Operations\nDetects risky file access patterns:\n- Absolute file paths outside expected directories\n- Parent directory traversal (`..`)\n- Writing to system directories\n\n**Why dangerous?** Could lead to unintended file access, data loss, or system modification.\n\n## Usage Pattern: Pre-Publish Checklist\n\nBefore publishing any skill:\n\n```bash\n# 1. Run security scan\nsecurity_scan.py \u002Fpath\u002Fto\u002Fskill\n\n# 2. Review any warnings\n# If warnings appear, fix the code or document why it's safe\n\n# 3. Re-scan after fixes\nsecurity_scan.py \u002Fpath\u002Fto\u002Fskill\n\n# 4. Only publish if scan passes\nclawhub publish \u002Fpath\u002Fto\u002Fskill --slug my-skill ...\n```\n\n## Interpretation of Results\n\n### ✅ \"No security issues found\"\nCode appears safe. Proceed with publishing.\n\n### ⚠️  \"Warning\" (Yellow)\nPotentially risky pattern detected. Review the specific line and decide:\n- **Is it legitimate?** Document why in code comments or SKILL.md\n- **Can it be avoided?** Refactor to safer alternatives\n- **Is it necessary?** Clearly document the risk and purpose\n\n### 🔴 \"Possible hardcoded secret\"\nSecret detected. Before publishing:\n- Remove the secret\n- Use environment variables instead: `os.getenv('API_KEY')`\n- Document required env variables in SKILL.md\n- Never commit real secrets\n\n## Examples\n\n### Legitimate os module usage (documented)\n```python\nimport os  # Used only for path.join() - safe file path construction\nworkspace = os.path.join(os.path.expanduser(\"~\"), \".openclaw\", \"workspace\")\n```\n\n**Scan result:** ⚠️ Warning about os import\n**Action:** Document safe usage pattern in code comments\n\n### Hardcoded secret (must fix)\n```python\nAPI_KEY = \"sk-1234567890abcdef\"  # DON'T DO THIS\n```\n\n**Scan result:** 🔴 Possible hardcoded secret\n**Action:** Remove and use environment variable:\n```python\nAPI_KEY = os.getenv(\"MY_SKILL_API_KEY\")\n# Document in SKILL.md: Requires MY_SKILL_API_KEY environment variable\n```\n\n### Safe pattern (no issues)\n```python\n# JSON storage for local data only\ndata = {\"notes\": [], \"metadata\": {}}\nwith open(\"data.json\", \"w\") as f:\n    json.dump(data, f)\n```\n\n**Scan result:** ✅ No issues\n\n## Best Practices\n\n1. **Always scan before publishing** - Make it part of your workflow\n2. **Review warnings manually** - The scanner can't judge context\n3. **Use environment variables for secrets** - Never hardcode\n4. **Prefer json over eval** - Safe parsing vs code execution\n5. **Document necessary risks** - If dangerous code is required, explain why\n6. **Minimize dangerous imports** - Only use what's truly necessary\n7. **Keep code simple** - Complex code is harder to audit\n\n## Integration with Development Workflow\n\n### Before committing to repo\n```bash\n# Pre-commit hook concept\npython3 \u002Fpath\u002Fto\u002Fsecurity_scan.py scripts\u002F\nif [ $? -ne 0 ]; then\n    echo \"❌ Security scan failed. Fix issues before committing.\"\n    exit 1\nfi\n```\n\n### Automated pre-publish check\n```bash\n#!\u002Fbin\u002Fbash\n# publish-safe.sh\n\nSKILL_PATH=$1\n\necho \"🔒 Running security scan...\"\npython3 \u002Fpath\u002Fto\u002Fsecurity_scan.py \"$SKILL_PATH\"\n\nif [ $? -ne 0 ]; then\n    echo \"❌ Cannot publish: Security scan failed\"\n    exit 1\nfi\n\necho \"✅ Security scan passed\"\nclawhub publish \"$SKILL_PATH\"\n```\n\n## Limitations\n\nThis scanner:\n- **Can't judge context** - Some dangerous code may be legitimate\n- **Static analysis only** - Doesn't execute code\n- **Python-focused** - Other languages need different tools\n- **Basic patterns** - Sophisticated obfuscation may evade detection\n\n**Complement with:**\n- Manual code review\n- Testing in isolated environment\n- Reading through all code before publishing\n- Using additional tools: `bandit`, `safety`\n\n## Trust Building\n\nPublishing skills that pass security scans builds trust in the community:\n- Users know you care about safety\n- Your reputation improves\n- Skills get adopted more readily\n- ClawHub may highlight safe skills\n\n## Examples of Published Skills (All Scanned)\n\n```bash\n# research-assistant\nsecurity_scan.py \u002Fhome\u002Fubuntu\u002F.openclaw\u002Fworkspace\u002Fskills\u002Fresearch-assistant\n# ✅ All clear\n\n# task-runner  \nsecurity_scan.py \u002Fhome\u002Fubuntu\u002F.openclaw\u002Fworkspace\u002Fskills\u002Ftask-runner\n# ✅ All clear\n\n# security-checker\nsecurity_scan.py \u002Fhome\u002Fubuntu\u002F.openclaw\u002Fworkspace\u002Fskills\u002Fsecurity-checker\n# ✅ All clear\n```\n\nAll three skills passed security scans before publishing to ClawHub.\n","# Security Checker\n\nSecurity scan Python skills before publishing to ensure code safety.\n\n## Quick Start\n\n```bash\nsecurity_scan.py \u003Cfile_or_directory>\n```\n\n**Examples:**\n```bash\n# Scan a single Python file\nsecurity_scan.py scripts\u002Fmy_script.py\n\n# Scan an entire skill directory\nsecurity_scan.py \u002Fpath\u002Fto\u002Fskill-folder\n\n# Scan multiple skills\nsecurity_scan.py skills\u002F\n```\n\n## What It Checks\n\n### Dangerous Imports\nDetects imports that could be used maliciously:\n- `os` - System-level operations\n- `subprocess` - Command execution\n- `shutil` - File operations\n- `socket` - Network operations\n- `urllib` \u002F `requests` - HTTP requests\n\n**Why dangerous?** These imports enable system command execution, file manipulation, and network access that could be exploited.\n\n### Dangerous Functions\nDetects potentially unsafe function calls:\n- `os.system()` - Executes shell commands\n- `subprocess.call()`, `subprocess.run()`, `subprocess.Popen()` - Command execution\n- `eval()` - Executes arbitrary code\n- `exec()` - Executes arbitrary code\n\n**Why dangerous?** These can execute arbitrary commands or code, leading to remote code execution vulnerabilities.\n\n### Hardcoded Secrets\nDetects tokens, keys, and passwords:\n- API keys\n- Auth tokens (including ClawHub tokens)\n- Passwords\n- Private keys\n- JWT-like tokens\n\n**Why dangerous?** Secrets leaked in published code can be stolen and abused.\n\n### Unsafe File Operations\nDetects risky file access patterns:\n- Absolute file paths outside expected directories\n- Parent directory traversal (`..`)\n- Writing to system directories\n\n**Why dangerous?** Could lead to unintended file access, data loss, or system modification.\n\n## Usage Pattern: Pre-Publish Checklist\n\nBefore publishing any skill:\n\n```bash\n# 1. Run security scan\nsecurity_scan.py \u002Fpath\u002Fto\u002Fskill\n\n# 2. Review any warnings\n# If warnings appear, fix the code or document why it's safe\n\n# 3. Re-scan after fixes\nsecurity_scan.py \u002Fpath\u002Fto\u002Fskill\n\n# 4. Only publish if scan passes\nclawhub publish \u002Fpath\u002Fto\u002Fskill --slug my-skill ...\n```\n\n## Interpretation of Results\n\n### ✅ \"No security issues found\"\nCode appears safe. Proceed with publishing.\n\n### ⚠️  \"Warning\" (Yellow)\nPotentially risky pattern detected. Review the specific line and decide:\n- **Is it legitimate?** Document why in code comments or SKILL.md\n- **Can it be avoided?** Refactor to safer alternatives\n- **Is it necessary?** Clearly document the risk and purpose\n\n### 🔴 \"Possible hardcoded secret\"\nSecret detected. Before publishing:\n- Remove the secret\n- Use environment variables instead: `os.getenv('API_KEY')`\n- Document required env variables in SKILL.md\n- Never commit real secrets\n\n## Examples\n\n### Legitimate os module usage (documented)\n```python\nimport os  # Used only for path.join() - safe file path construction\nworkspace = os.path.join(os.path.expanduser(\"~\"), \".openclaw\", \"workspace\")\n```\n\n**Scan result:** ⚠️ Warning about os import\n**Action:** Document safe usage pattern in code comments\n\n### Hardcoded secret (must fix)\n```python\nAPI_KEY = \"sk-1234567890abcdef\"  # DON'T DO THIS\n```\n\n**Scan result:** 🔴 Possible hardcoded secret\n**Action:** Remove and use environment variable:\n```python\nAPI_KEY = os.getenv(\"MY_SKILL_API_KEY\")\n# Document in SKILL.md: Requires MY_SKILL_API_KEY environment variable\n```\n\n### Safe pattern (no issues)\n```python\n# JSON storage for local data only\ndata = {\"notes\": [], \"metadata\": {}}\nwith open(\"data.json\", \"w\") as f:\n    json.dump(data, f)\n```\n\n**Scan result:** ✅ No issues\n\n## Best Practices\n\n1. **Always scan before publishing** - Make it part of your workflow\n2. **Review warnings manually** - The scanner can't judge context\n3. **Use environment variables for secrets** - Never hardcode\n4. **Prefer json over eval** - Safe parsing vs code execution\n5. **Document necessary risks** - If dangerous code is required, explain why\n6. **Minimize dangerous imports** - Only use what's truly necessary\n7. **Keep code simple** - Complex code is harder to audit\n\n## Integration with Development Workflow\n\n### Before committing to repo\n```bash\n# Pre-commit hook concept\npython3 \u002Fpath\u002Fto\u002Fsecurity_scan.py scripts\u002F\nif [ $? -ne 0 ]; then\n    echo \"❌ Security scan failed. Fix issues before committing.\"\n    exit 1\nfi\n```\n\n### Automated pre-publish check\n```bash\n#!\u002Fbin\u002Fbash\n# publish-safe.sh\n\nSKILL_PATH=$1\n\necho \"🔒 Running security scan...\"\npython3 \u002Fpath\u002Fto\u002Fsecurity_scan.py \"$SKILL_PATH\"\n\nif [ $? -ne 0 ]; then\n    echo \"❌ Cannot publish: Security scan failed\"\n    exit 1\nfi\n\necho \"✅ Security scan passed\"\nclawhub publish \"$SKILL_PATH\"\n```\n\n## Limitations\n\nThis scanner:\n- **Can't judge context** - Some dangerous code may be legitimate\n- **Static analysis only** - Doesn't execute code\n- **Python-focused** - Other languages need different tools\n- **Basic patterns** - Sophisticated obfuscation may evade detection\n\n**Complement with:**\n- Manual code review\n- Testing in isolated environment\n- Reading through all code before publishing\n- Using additional tools: `bandit`, `safety`\n\n## Trust Building\n\nPublishing skills that pass security scans builds trust in the community:\n- Users know you care about safety\n- Your reputation improves\n- Skills get adopted more readily\n- ClawHub may highlight safe skills\n\n## Examples of Published Skills (All Scanned)\n\n```bash\n# research-assistant\nsecurity_scan.py \u002Fhome\u002Fubuntu\u002F.openclaw\u002Fworkspace\u002Fskills\u002Fresearch-assistant\n# ✅ All clear\n\n# task-runner  \nsecurity_scan.py \u002Fhome\u002Fubuntu\u002F.openclaw\u002Fworkspace\u002Fskills\u002Ftask-runner\n# ✅ All clear\n\n# security-checker\nsecurity_scan.py \u002Fhome\u002Fubuntu\u002F.openclaw\u002Fworkspace\u002Fskills\u002Fsecurity-checker\n# ✅ All clear\n```\n\nAll three skills passed security scans before publishing to ClawHub.\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fjohstracke\u002Fsecurity-checker",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill security-checker",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill security-checker",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill security-checker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fjohstracke\u002Fsecurity-checker\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]