Security

batteryshark Bundle

Audit, disable, and restore selected Windows AI features through reviewable registry and policy changes with explicit elevation and verification.

batteryshark Bundle

Audit repositories and public documentation for internal notes, defensive explanations, unexplained assertions, stale project residue, hidden assumptions, and generated-sounding meta commentary. Use when scanning launch material, cleaning public prose, or deciding which reasoning belongs outside the finished deliverable.

batteryshark Bundle

Audit an interface for design failures, from source alone — a changed diff or a whole workspace. Hunts eight failure classes (controls that never earned their place, orphaned capabilities, scentless labels, excise steps, recall demands, mute actions, slip traps, state amnesia) across screens, forms, navigation, CLI commands, and error messages, and returns ranked one-line findings with fixes, citing file and line. Use to audit an interface or UX, review an interface change, find out why users cannot find features, or decide what a UI should drop. Reports only; does not apply fixes. Not for code quality, correctness, or security review.

batteryshark Bundle

Audit and improve a portable skill for contract compliance, triggering, progressive disclosure, script correctness, portability, safety, and verification. Use for skill reviews, pre-publication checks, broken-skill diagnosis, quality scoring, or modernizing an older package to the Skill Tap contract.

batteryshark Bundle

Audit and modernize Node.js scripts inside portable skills with explicit dependencies, committed lockfiles, local npm commands, compiled runnable JavaScript, and no global-tool assumptions. Use when a skill contains JavaScript or TypeScript, relies on global npm installs, lacks deterministic setup, or fails when copied to another machine.

batteryshark Bundle

Audit or plan a single-player falling-tetromino implementation against an explicit historical gameplay baseline covering field geometry, seven-bag generation, controls, lock-down, scoring, spins, game-over, UI, and audio. Use for evidence-based implementation reviews or remediation plans; this is an unofficial engineering checklist, not Tetris certification.

batteryshark Bundle

Audit and modernize Python scripts inside portable skills with PEP 723 dependency metadata, stable uv launchers, standard-library fallbacks, and no hidden virtualenv or global-package assumptions. Use when a skill invokes Python directly, has undeclared imports, fails outside its author’s machine, or needs contract-compliant bin and scripts structure.

borski Skill

Audit and tend to existing travel reservations. Reads a user-provided reservations file, then systematically checks every booking for price drops, better cabin availability, improved routings, schedule changes, nearby airport alternatives, and award repricing opportunities. Invoke proactively on a regular cadence or when the user says "garden", "check my bookings", "audit reservations", "price drop", "better routing", "did my flight change", "tend reservations", "reservation maintenance", or "check my trips".

sethgammon Bundle

5-pass structured code review — correctness, security, performance, readability, consistency

sethgammon Bundle

Cross-drive storage audit and cleanup. Surveys all drives, finds orphaned git worktrees, large AI tool caches (.ollama, .gemini, .cursor, npm, pip), and buildable artifacts (node_modules, .venv). Produces a prioritized action plan with specific migration commands. Use when disk space is low or worktrees need cleanup; do NOT use for project structure issues (use /organize instead).

yosefhayim Bundle

Create or edit a project's landing documentation set — README.md, AGENTS.md, CLAUDE.md, .github/copilot-instructions.md, and llms.txt — by first deciding which artifacts the repo actually needs, then grilling the user one question at a time with recommended defaults, building a compact README map, using official hyperlinks for named tools and technologies, and only then writing. Inspects the repo before asking anything discoverable. Use when the user wants to create, write, edit, rewrite, audit, polish, or "fix up" a README, AGENTS.md, CLAUDE.md, Copilot instructions, llms.txt, or any project landing/onboarding docs.

yosefhayim Skill

Use when the user asks to build or replace a feature and wants existing repository code, platform capabilities, installed dependencies, packages, templates, or official ecosystem options checked before new implementation.

yosefhayim Skill

Review a large changeset (a branch, working tree, or PR — tens to hundreds of files) against a repo's code-style.rules.json so the user can trust it WITHOUT reading every diff, and LEARN the architecture from a short teaching report instead. Runs Biome (+ its grit plugins) to auto-fix the mechanical/structural channels across all files, then fans out sub-agents over the diff to check only the judgment-channel rules + the user's original intent, and returns a deviations-only report that opens with a layer/flow map of what changed and teaches the "why" behind each finding. Use when reviewing/auditing a big diff, a PR, or an AI-generated changeset, or the user says "review this", "can I trust this diff", "audit these changes". To coach while building, use grill-me-code-style-coach; to create the ruleset, grill-me-code-style.

drmoisan Skill

Invoke the epic-review worker to produce epic-audit artifacts for an epic folder.

drmoisan Skill

Invoke the feature-review worker to produce feature-audit artifacts for an active feature folder.

waseemnasir2k26 Skill

One-command laptop security sweep + speed/hardening pass for Windows (Jarvis core). Read-only audit first (Defender status, threat history, live connections, listening ports, firewall, autoruns, scheduled tasks, network neighbors), then OPTIONAL hardening (Public firewall inbound block, disable SMB1, remove Lenovo SoftLanding bloat) and OPTIONAL cleanup (measure %TEMP%/caches/Recycle Bin, then clean safe targets). Ends with a hardware verdict (RAM / SSD vs HDD / CPU / free disk / power plan). Use when user says "run jarvis", "antivirus scan", "scan my laptop", "scan my network", "is my laptop safe", "clean temp files", "make my laptop faster", "security check", "/jarvis-secure", "harden my pc", or asks to check the machine/network for threats.

haohao-end Bundle

Security Ownership Map

haohao-end Bundle

Security Best Practices

hantechnology Skill

Compatibility wrapper: Redirect to `/impeccable audit`.

hantechnology Bundle

Deliver application and platform security guidance for auth, authz, secure coding, secrets, vulnerability review, and compliance-adjacent hardening without tying decisions to one stack.

layneformalized225 Bundle

Monthly self-deception audit — 25 anti-patterns from CEO Bible Section M

philrobinluo Bundle

安装前对 Skill 做静态证据审计、权限建模和人工复核，不把一次扫描当作安全证明。 当用户需要把相关任务变成有证据、可验证的交付时使用。

advaitpaliwal Skill

Predict or audit protein structures with AlphaFold2-style workflows. Use when a research task needs monomer/multimer structure prediction, MSA/template handling, confidence metrics, or comparison against PDB/AlphaFold references.

devton Skill

agentic-workflows-blueprint.workflow.implementing-devsecops-security-scanning

devton Skill

agentic-workflows-blueprint.workflow.implementing-pod-security-admission-controller

devton Skill

agentic-workflows-blueprint.workflow.performing-container-security-scanning-with-trivy

guoliang1114-boop Skill

起草审计报告，基于ISA 700/701/706框架，覆盖意见类型决策逻辑、关键审计事项、强调事项段等。

guoliang1114-boop Skill

制定集团审计策略，基于ISA 600框架，覆盖组成部分识别、重要性分配、组成部分审计师协调和合并程序。

guoliang1114-boop Bundle

基于 ISA 315 (Revised 2019) 框架执行审计计划阶段的风险评估。当用户需要 (1) 制定审计计划 (2) 识别重大错报风险 (3) 评估内部控制 (4) 确定重要性水平 (5) 设计审计策略 时使用。输出结构化风险评估文档。

guoliang1114-boop Skill

基于IIA绩效标准执行内部审计项目，涵盖审计目标、范围、程序、抽样方法和工作底稿编制

guoliang1114-boop Skill

基于IIA国际内部审计专业实务标准，制定风险导向的年度内部审计计划，涵盖审计宇宙、风险评分、资源分配

guoliang1114-boop Skill

设计和执行实质性审计程序，覆盖细节测试、实质性分析程序、函证程序和审计抽样，基于ISA 330框架。

hiteshbandhu Bundle

UI/UX and product review for web interfaces — opinionated principles, checklist-driven audits, polish passes on screenshots, and pre-ship UI gates. Uses Playwright to navigate, screenshot, and smoke-test interactions when a URL is available. Triggers on "review my UI", "polish this", "UX audit", "fix the hero", "make it look professional", "ui pass", "design review", attaches screenshot with UI feedback. Use when building or reviewing interfaces and product flows, not generic code review.

hiteshbandhu Bundle

Pre-ship gate before commit or push — runs lint, typecheck, tests, build, secret scan, and git diff review, then outputs a READY/BLOCKED verdict with a proposed commit message. Never commits without explicit user confirmation. Triggers on "ship check", "ready to commit", "pre-push check", "commit and push", "ship this", "can I push".

hiteshbandhu Bundle

Build and check UI the way a person meets it — measure the rendered page instead of trusting the source, break it on purpose at several widths and along the paths people actually take, fix the root cause, and re-measure before calling it done. Carries a catalogue of UI failures that survive code review (clipped borders, dropped size classes, dead ends on short screens, stale caches, redirects that never move the URL) with symptom → cause → fix. Triggers on "verify this UI", "does this look right", "check it at other widths", "it looks bad, fix it", "break the product", "make these pages consistent", "why is this clipped / overflowing / huge / not clickable", "audit every page in this section", and any screenshot sent with "fix this".

int2t05 Bundle

Use when the code is too complex — clarity over cleverness, removes speculative abstractions, dead complexity, and earns-its-cost structures. Triggers on "simplify", "too complex", "refactor for clarity", "简化", "太复杂", "重构求清晰". Not for cross-module structural changes (use refactoring) or architecture audit (use codebase-design) — single-file clarity stays here.