privilege-declaration-generator
Generates tizen-manifest.xml and config.xml privilege declarations. Auto-detects required privileges from app source code.
Discover documentation automation tools skills, compare source repositories and read the instructions for each workflow.
Generates tizen-manifest.xml and config.xml privilege declarations. Auto-detects required privileges from app source code.
Rapidly find and reclaim disk storage by identifying build artifacts, git garbage, temp files, and other space hogs. Use when disk is full or running low on space.
Review security fixes and patches for completeness and correctness.
Security-focused code review of diffs and pull requests using Trail of Bits expertise.
Automated code review for pull requests using specialized review patterns.
Find similar vulnerabilities and bugs across codebases using pattern-based analysis. Use when hunting bug variants, building CodeQL/Semgrep queries, analyzing security vulnerabilities, or performing systematic...
Parse, analyze, and process SARIF (Static Analysis Results Interchange Format) files. Use when reading security scan results, aggregating findings from multiple tools, deduplicating alerts, extracting specific...
Generates secure Tizen app projects (native/web/.NET) with privilege declarations, SMACK labels, and secure storage templates pre-configured.
GitHub CLI for repository management. Issues, PRs, releases, and API queries from the command line.
Run Semgrep static analysis for fast security scanning and pattern matching. Use when asked to scan code with Semgrep, write custom YAML rules, find vulnerabilities quickly, use taint mode, or set up Semgrep in...
This skill should be used when the user asks to "scan for TODOs", "find placeholders", "clean up stubs", "remove temporary code", "audit for incomplete code", or "erase substitutions from codebase". Scans exist...
Guide you through Trail of Bits' 5-step secure development workflow. Runs Slither scans, checks special features (upgradeability/ERC conformance/token integration), generates visual security diagrams, helps doc...
Prepare your codebase for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates com...
Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.
DeepWiki MCP server for AI-powered GitHub repository documentation and
コード変更を検出し、関連ドキュメントを自動更新。git diffからAPIエンドポイント、スキーマ、設定ファイルの変更を特定し、対応するドキュメントを同期。
AI-assisted filtering to identify and remove non-useful documentation files. Generates review manifests and applies deletion lists.
Guide for simplifying and refining code after coding sessions. Use when cleaning up complex code, reviewing PRs for readability, or applying consistent refactoring patterns.
Provides code auditing methodology, checklists, and best practices. Use when user asks to "audit code", "find technical debt", "security review", "identify dead code", "analyze code quality", or "check best pra...
Keep project documentation current and optimized for AI agents. Use when user asks to "update docs", "sync documentation", "update CLAUDE.md", "update README", "check documentation freshness", "document recent...
This skill should be used when the user asks to "set up release please", "configure automated releases", "manage version numbers", "add changelog automation", or mentions release-please, semantic versioning, or...
This skill should be used when the user asks to "create a hook", "add a hook", "write a hook", or mentions Claude Code hooks. Also suggest this skill when the user asks to "automatically do X" or "run X before/...
Fetch code from GitHub repositories as LLM-friendly context. Use when needing to reference, analyze, or understand code from a GitHub repo/directory/file.
Generate navigational codebase maps with architecture diagrams. Use when mapping a codebase, creating architecture docs, visualizing project structure, generating infrastructure diagrams, understanding repo lay...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.