Security

data-wise Bundle

This skill should be used when the user asks to "create CLAUDE.md", "scaffold CLAUDE.md", "sync CLAUDE.md", "update CLAUDE.md", "audit CLAUDE.md", "fix CLAUDE.md", "optimize CLAUDE.md", "edit CLAUDE.md sections", or otherwise wants to manage the CLAUDE.md lifecycle (init, sync, edit). Covers project-local and global (`~/.claude/CLAUDE.md`) files. For applying suggestions from the /insights report specifically, use the `insights-apply` skill instead.

data-wise Bundle

This skill should be used when the user asks to "audit commands", "check command frontmatter", "audit skills", "check skill standards", "validate command/skill health", or invokes `/craft:code:command-audit` or `/craft:code:skill-standards`. Shared vocabulary + reference bodies for craft's two schema-audit commands — both validate craft's own frontmatter (commands/skills/agents vs `_schema.json`, or `skills/**/SKILL.md` vs Anthropic's authoring standards) and share the same `--format`/`--fix` semantics. Not for dependency or docs-site checks — see `/craft:code:deps-audit`, `/craft:code:deps-check`, `/craft:code:docs-check` instead, which are unrelated generic cross-project tools despite living in the same `commands/code/` directory.

data-wise Skill

This skill should be used when the user asks to "audit my plugins", "check for plugin duplicates", "plugin collision check", "find duplicate skills across plugins", "which plugins overlap", or wants to know if an installed Claude Code plugin duplicates or shadows another plugin's commands/skills. Diffs enabled plugins' actual command/skill surface against each other and flags cross-namespace name collisions — e.g. a bare `workflow:brainstorm` skill in one plugin vs. `craft:brainstorm` in another. Read-only — reports findings, never disables or uninstalls a plugin itself. Do not confuse with guard-audit (branch-guard.sh rule tuning) or command-skill-token-efficiency (command-vs-skill placement within a single plugin) — this skill compares surfaces ACROSS installed plugins.

data-wise Skill

This skill should be used when the user asks to "create a Homebrew formula", "fix brew audit errors", "write a formula", "Homebrew best practices", or needs help with Homebrew formula syntax, dependencies, and troubleshooting. Expert knowledge of Homebrew formula creation and maintenance.

45ck Bundle

Normalize UI terminology by creating a canonical glossary of nouns, verbs, statuses, and labels used across the system.

45ck Bundle

Audit a prototype for cross-screen consistency in navigation, actions, states, patterns, and interaction rules.

45ck Bundle

Audit all failure paths, edge cases, and non-happy-path states -- empty states, validation errors, permission failures, loading, undo, and recovery.

45ck Bundle

Audit UI terminology and create Beads issues from the findings. Converts terminology drift, overloaded terms, and vague labels into trackable Beads tasks with priorities and dependencies.

45ck Bundle

Audit cross-screen consistency and create Beads issues from the findings. Converts consistency breaks and invariant violations into trackable Beads tasks with priorities and dependencies.

45ck Bundle

Audit failure paths and create Beads issues from the findings. Converts unhandled failure states, missing empty states, and broken recovery paths into trackable Beads tasks with priorities and dependencies.

emaraschio Bundle

Scoped, plan-first workflow for large "check-N-things" tasks (audits, inventories, catalogs, large migrations, cross-checks). Decomposes the surface, fans out capped parallel subagents, verifies findings before reporting, and gates any change behind explicit approval. Use for "audit X for Y", "find all", "catalog every", "inventory", "migrate across", or any repeatable workflow that has quietly become "check 400 things".

emaraschio Bundle

Security audit of codebase or change

emaraschio Bundle

Act as an AI operations consultant: interview how a business function's workflows actually run, label each step Human-only / AI-assisted / AI-owned, pick the highest-ROI automation tied to money, margin, or output, warn on AI theater and distraction traps, and recommend one narrow one-week test. Use for automation ROI, workflow AI map, ops consultant, or "where should AI help".

drmoisan Skill

Review a feature branch relative to a base branch and write audit artifacts into the active feature folder. Use when Codex must produce policy, code, and feature audits and trigger remediation planning when needed.

khasky Skill

Designs or reviews the shape of an HTTP API before code exists — resources, versioning, pagination, idempotency, filtering, and where the error contract plugs in. Use when asked to design or review an API, decide versioning or pagination, add an endpoint at the design stage, 'спроектируй API', or when awesome-design-doc needs the contract detailed. Do not use for the error envelope itself (awesome-error-standards), vulnerability review of handlers (awesome-security-audit), or auditing an implemented architecture (awesome-architecture-audit).

khasky Bundle

Produces a design document or ADR for a feature or architectural decision: requirements and scale numbers first, real alternatives with trade-offs, a recommendation grounded in the requirements, explicit non-goals and migration path. Use when asked to write a design doc, write an ADR, decide which approach to take, run a pre-mortem on a plan before committing to it, 'спроектируй', 'сделай pre-mortem', or when awesome-code-review requests an ADR for a load-bearing decision. Do not use for auditing an existing architecture (awesome-architecture-audit) or for HTTP resource modeling detail (awesome-api-design).

khasky Skill

Read-only audit of a repository for machine-written 'AI slop' across code, comments, tests, docs, configs and CI, against a verified catalog: glyph pockets, stale and false comments, change-narration, drift-bait numbers, template stamps, impossible defensiveness, copy-paste drift, negative-parallelism prose. Every suspect is verified against the code, absence is proven per category, and the ranked findings hand off to awesome-code-cleanup, which owns every edit. Use when asked to find AI slop or machine-written markers, or 'проверь код на следы ИИ'. Do not use to fix what it finds, for prose line-editing (awesome-document-style), or for public-claims drift (awesome-claims-audit).

khasky Bundle

Reviews a diff, patch or pull request for correctness, security and team standards, with confidence-scored findings in severity buckets (Critical / Suggestions / Nice to have). Use when asked to review a change, before merging, after finishing a feature, or 'сделай ревью'. Do not use for responding to review feedback you received (awesome-code-review-feedback) or for docs-only and formatting-only changes.

khasky Skill

Repo-wide cleanup of AI-like code noise, behavior-preserving: a comment pass (delete narration, condense bloat, fix stale, keep load-bearing), a read-only audit mode, an opt-in refactor mode for vague names and over-abstraction, a detection mode for dead code and logical inconsistencies, and an execution mode that applies another audit's findings. Use when asked to clean up or condense comments, de-slop vibe-coded files, apply a YAGNI pass, find dead code, apply a slop-audit report, or 'почисти код', 'найди мёртвый код'. Do not use for prose (awesome-humanize-en, awesome-document-style) or for the read-only marker sweep (awesome-slop-audit), whose report it executes.

khasky Bundle

Designs and writes tests that catch real regressions — placement (unit/integration/E2E), factories and fixtures, behavior-first assertions, characterization tests for legacy code, property/fuzz tests for parsers. Use when asked to write tests or add coverage for a module, 'напиши тесты', when a bug fix needs its regression test, or when awesome-bug-fix, awesome-code-review or awesome-security-audit calls for one. Do not use for judging existing tests in a review (awesome-code-review) or for diagnosing the bug itself (awesome-bug-fix).

khasky Skill

Read-only audit of third-party dependencies — lockfile discipline, typosquats and hallucinated package names, dependency confusion, install-script exposure, provenance, licenses, CVE reachability — with a SHIP / FIX / BLOCK verdict. Use when asked to audit dependencies or the supply chain, judge whether a package is safe, review a manifest change, after a bot version bump, or 'проверь зависимости'. Do not use for vulnerabilities in your own code (awesome-security-audit) or to execute the upgrades (awesome-dependency-upgrade).

khasky Skill

Erases a repository's entire git history and replaces it with a single fresh commit, then force-pushes — safely: access checks, a verified mirror backup, a secret scan, and a confirmation gate before anything irreversible. Takes a repository URL. Use when asked to wipe git history, squash every commit into one Initial commit, start the history fresh, or 'очистить историю git'. Do not use to squash a feature branch before merge (an interactive rebase) or to remove one secret from history (git-filter-repo plus rotation).

khasky Bundle

Read-only whole-project audit of design: module boundaries and dependency direction, docs-vs-code fidelity, YAGNI/KISS/SOLID, and extensibility (build from source, add a provider), producing a prioritized report with a SHIP / FIX / BLOCK verdict. Language-agnostic. Use when asked to audit the architecture of a whole codebase, check whether the docs still match the code, judge how hard it is to extend, or 'оцени архитектуру'. Do not use for one diff (awesome-code-review), a vulnerability (awesome-security-audit), runtime latency (awesome-performance-audit), or comment cleanup (awesome-code-cleanup).

khasky Skill

Plans and executes dependency upgrades safely — batching by risk, changelog-driven major migrations, overrides for unfixed CVEs, verification between steps, one revertable commit per batch. Use when asked to upgrade or bump dependencies, act on an awesome-dependency-audit report, or 'обнови зависимости'. Do not use for detection and risk assessment (awesome-dependency-audit); adding a brand-new dependency is an ask-first decision outside this skill.

lqf0624 Bundle

Workflow-first research skill pack for computer systems, networking, and AI papers. Use when Codex needs to scope a paper or multi-paper program, design methods within a fixed topic, test novelty, map literature, plan and audit experiments, write and visualize results, simulate review, or prepare a submission and rebuttal for systems and AI venues.

lqf0624 Bundle

Experiment-planning skill for research papers in systems, networking, and AI. Use when Codex must design or audit baselines, metrics, workloads, ablations, statistical checks, scaling studies, sensitivity analysis, and failure tests so that a paper's claims are actually supported.

ww-w-ai Skill

Code review skill for analyzing code quality, detecting bugs, and ensuring best practices. Use proactively when user requests code review, quality check, or bug detection. Triggers: code review, review code, check code, analyze code, bug detection, 코드 리뷰, 코드 검토, 버그 검사, コードレビュー, バグ検出, 代码审查, 代码检查, revisión de código, detección de errores, revue de code, détection de bugs, Code-Review, Fehlererkennung, revisione del codice, rilevamento bug Do NOT use for: design document creation, deployment tasks

ww-w-ai Skill

bkend.ai operational guides, troubleshooting, and platform comparison. Covers migration guides, performance optimization, testing strategy, common error solutions, and FAQ. Triggers: migration, troubleshoot, FAQ, performance, error handling, comparison, 마이그레이션, 문제해결, 자주 묻는 질문, 성능, 에러, マイグレーション, トラブルシューティング, FAQ, パフォーマンス, 迁移, 故障排除, 常见问题, 性能, 错误处理, migracion, solucion de problemas, preguntas frecuentes, rendimiento, migration, depannage, FAQ, performance, gestion des erreurs, Migration, Fehlerbehebung, FAQ, Leistung, Fehlerbehandlung, migrazione, risoluzione problemi, FAQ, prestazioni, gestione errori Do NOT use for: authentication implementation (use bkend-auth), database schema design (use bkend-data), security setup (use bkend-security)

ww-w-ai Skill

Skill for verifying codebase quality and gap analysis. Covers architecture consistency and convention compliance. Use proactively when implementation is complete and quality verification is needed. Triggers: code review, architecture review, quality check, gap analysis, 코드 리뷰, 설계-구현 분석, コードレビュー, ギャップ分析, 代码审查, 差距分析, revisión de código, análisis de brechas, revue de code, analyse des écarts, Code-Review, Gap-Analyse, revisione del codice, analisi del divario Do NOT use for: initial planning, design creation

atrislabs Skill

Audit and improve Claude skills against the Anthropic skill guide. Use when creating new skills, improving existing ones, or preparing skills for ClawHub distribution. Triggers on skill audit, improve skill, new skill, skill quality, or ClawHub publish.

cyberuni Skill

Scaffold and ship a new SKILL.md through the full creation lifecycle — design, implement, structural audit, trigger eval, and evidence recording. Use when creating a skill from scratch or formalizing an existing one, even if the user just says "I want a skill for X" or "help me build this."

archibate Skill

Review code for AI slop patterns. TRIGGER when user says "review for AI slop", "check for AI patterns", "clean up AI code", "audit AI-generated code", or "review AI slop".

htlin222 Skill

Security audits and secure coding. Use for vulnerability detection or auth implementation.

frankxai Skill

The substrate operating brain for building income systems with AI agents. Use when planning, building, or scaling an affiliate/content/product income network — deciding what to build next, where money actually comes from, how to make it compound, and how the system improves itself. Portable and brand-neutral. Composes affiliate-audit. Trigger phrases: build an income system, make money with agents, scale my content network, what should I build next, passive income with AI, monetize this site, agentic income.

frankxai Skill

Map which content mentions paying tools but lacks affiliate links, and which programs to join first. Use when monetizing tool-comparison content, choosing affiliate programs, or auditing a passive-income site's link coverage. Portable and brand-neutral. Trigger phrases: affiliate audit, affiliate link, affiliate program, monetization gap, link coverage, which programs to join, missing affiliate links, audit my content, program catalog.

frankxai Bundle

Design safe, private-first Notion operating systems, estate audits, parallel rebuilds, template systems, and public mirrors. Use when asked to map a Notion workspace, clean or restructure Notion, create business/personal Notion dashboards, build reusable Notion templates, or turn private Notion content into sanitized public docs. Portable and brand-neutral. Trigger phrases: map my Notion, Notion estate audit, restructure Notion, Notion operating system, Notion dashboard, Notion template system, publish Notion docs.