← all publishers

florianbuetow

@florianbuetow source repo

121 published skills · page 2 of 2

  1. Race Conditions · florianbuetow bundle
    This skill should be used when the user asks to "check for race conditions", "find TOCTOU bugs", "analyze concurrency issues", "detect double-spend vulnerabilities", "check for check-then-act patterns", "find shared state bugs", or mentions "race condition", "TOCTOU", "double-spend", "concurrency", "atomicity", or "thread safety" in a security context.
    0
    installs
  2. Agent Guardrails Update · florianbuetow
    Re-analyze Claude Code session logs against existing agent guardrail rules to measure effectiveness, catch false positives, identify missed anti-patterns, and refine regex patterns. Use when user asks to "update guardrails", "refine guardrail rules", "check guardrail effectiveness", "agent-guardrails update", "tune guardrails", or wants to improve existing behavioral rules based on real usage data.
    0
    installs
  3. Pasta Attack Sim · florianbuetow
    This skill should be used when the user asks to "simulate attacks", "build attack trees", "model exploit chains", "score exploitability", or is running PASTA stage 6. Also triggers when the user asks about attack scenarios, red team simulation, DREAD scoring, or detection gap analysis in a threat modeling context. Part of the PASTA threat modeling methodology (Stage 6 of 7).
    0
    installs
  4. Pasta Objectives · florianbuetow
    This skill should be used when the user asks to "define business objectives", "identify business-critical assets", "determine risk appetite", or is running PASTA stage 1. Also triggers when the user asks about compliance requirements, acceptable risk thresholds, or business impact analysis in a threat modeling context. Part of the PASTA threat modeling methodology (Stage 1 of 7).
    0
    installs
  5. Cache Money · florianbuetow bundle
    This skill should be used when the user asks to "keep cache warm", "warm the cache", "save tokens", "reduce token usage", "cache-money", "start cache ping", "optimize peak hours", "prevent cache expiry", or mentions Anthropic prompt caching, cache TTL, peak hour throttling, token cost optimization, or keeping the context cache alive in Claude Code sessions.
    0
    installs
  6. Spec Writer · florianbuetow bundle
    An expert-guided skill for creating layered software specification documents for greenfield projects. Produces five document types: Vision, Business Requirements (BRS), Software Requirements (SRS), Architecture & Design, and Behavioral Spec & Test Verification. Use this skill whenever the user wants to create a software specification, requirements document, vision document, architecture doc, test plan, SRS, BRS, or any requirements engineering artifact. Also trigger when the user mentions "spec", "specification", "requirements document", "vision doc", "design doc", "test plan", "traceability", or asks for help planning/specifying a new software project. Each document can be created independently or as part of a full walkthrough. The skill drives the conversation through clarifying questions, provides expert suggestions based on project context, and outputs polished markdown documents.
    0
    installs
  7. Agent Guardrails Analyze · florianbuetow
    Scan Claude Code chat session logs for recurring agent anti-patterns (hedging, stalling, skipping, false completions, preference-asking, dismissing, cosmetic, caveats, flagging) and produce a ranked report with frequency counts, example excerpts, and suggested guardrail rules. Use when user asks to "analyze sessions for anti-patterns", "find bad patterns in logs", "what anti-patterns am I seeing", "agent-guardrails analyze", or wants data-driven guardrail recommendations.
    0
    installs
  8. Agent Guardrails Install · florianbuetow
    Install agent behavioral guardrail rules into a project's .claude/ directory. Generates a Stop hook bash script and configures settings.local.json. Includes nine battle-tested rules (no-guessing, no-stalling, no-preference-asking, no-false-completion, no-skipping, no-dismissing, no-cosmetic, no-caveats, no-flagging). Use when user asks to "install guardrails", "set up agent guardrails", "add behavioral hooks", "agent-guardrails install", or wants to enforce assistant discipline.
    0
    installs
  9. Claudeignore · florianbuetow
    This skill should be used when the user wants to "create a claudeignore", "update claudeignore", "optimize context", "ignore folders", "reduce token usage", "set up .claudeignore", or mentions .claudeignore, context window optimization, or ignoring directories from Claude Code indexing.
    0
    installs
  10. Privilege Escalation · florianbuetow
    This skill should be used when the user asks to "check for privilege escalation", "analyze authorization risks", "find access control vulnerabilities", or mentions "elevation of privilege" in a security context. Maps to STRIDE category E.
    0
    installs
  11. Iso27001 Sdlc · florianbuetow bundle
    Scan a software repository for ISO 27001:2022 compliance of its software development controls. Produces a per-control compliance report covering Annex A controls 8.4, 8.25–8.33 (source code access, secure SDLC, application security requirements, secure architecture, secure coding, security testing, outsourced development, environment separation, change management, and test data). Use this skill whenever a user mentions ISO 27001, ISMS compliance, security audit readiness, Annex A controls, secure SDLC compliance, or wants to check whether their codebase meets information security standards. Also trigger when the user asks about audit preparation for software development, security control gaps, or compliance posture of a repository — even if they don't mention ISO 27001 by name but describe wanting to verify security practices against a standard.
    0
    installs
  12. Retrospective · florianbuetow bundle
    This skill should be used when the user asks to "run a retrospective", "review my sessions", "what went well", "what didn't go well", "how can I improve my workflow", "analyze my Claude usage", "suggest skills I should create", "what should I automate", "find workflow improvements", or "review how I work with Claude". Also triggers when the user mentions session analysis, workflow optimization, skill opportunities, subagent suggestions, slash command ideas, or asks about improving their AI-assisted development process. Supports analyzing all dimensions at once or focusing on a single dimension.
    0
    installs
  13. Tokeneconomics · florianbuetow bundle
    Analyze Claude Code session token usage to flag waste and optimization opportunities. Use when the user asks to "analyze token usage", "check token efficiency", "audit token spend", "tokeneconomics", "reduce token costs", "optimize token usage", "check my burn rate", or mentions token waste, session costs, usage limits, cache efficiency, or conversation sprawl.
    0
    installs
  14. Non Repudiation Privacy · florianbuetow
    This skill should be used when the user asks to "check for non-repudiation privacy risks", "analyze excessive audit logging", "find privacy issues related to accountability", "check for forced identity linking", or mentions "non-repudiation" in a privacy context. Maps to LINDDUN category N. This is the INVERSE of STRIDE repudiation -- here too much proof is the threat.
    0
    installs
  15. Progressive Disclosure Analyze · florianbuetow bundle
    This skill should be used when the user asks to "analyze documentation structure", "audit progressive disclosure", "map documentation references", "find orphaned docs", "check context rot risk", "audit CLAUDE.md", "audit AGENTS.md", or wants to understand how a repository's documentation is structured for AI agent consumption. Produces a disclosure map, orphan report, and anti-pattern findings.
    0
    installs
  16. Context Research · florianbuetow
    <!--
    0
    installs
  17. Solid Principles · florianbuetow bundle
    This skill should be used when the user asks to "check SOLID violations", "audit class design", "review code quality", "find design smells", or "improve object-oriented architecture". Also triggers when the user mentions a principle by name (e.g., "check SRP", "is this violating LSP?", "dependency inversion"), or asks about coupling, cohesion, or class responsibilities. Supports checking all five principles at once or focusing on a single principle.
    0
    installs
  18. Progressive Disclosure Restructure · florianbuetow bundle
    This skill should be used when the user asks to "restructure CLAUDE.md", "restructure AGENTS.md", "create a documentation index", "add a table of contents to CLAUDE.md", "organize project docs", "refactor root configuration file", "build a doc index", or wants to restructure how a repository's root configuration file references its documentation. Generates a thematic, book-style index in the highest-precedence root configuration file.
    0
    installs
  19. Progressive Disclosure · florianbuetow
    This skill should be used when the user asks to "analyze documentation structure", "audit progressive disclosure", "restructure CLAUDE.md", "restructure AGENTS.md", "create a documentation index", "organize project docs", "find orphaned docs", "map documentation references", "improve context loading", or mentions progressive disclosure, documentation hierarchy, root configuration file organization, or context rot prevention. Analyzes or restructures how a repository discloses documentation through root configuration files.
    0
    installs
  20. Beyond Solid Principles · florianbuetow bundle
    This skill should be used when the user asks to "check architecture principles", "audit system design", "review code for coupling", "find architecture smells", or "improve system-level design". Also triggers when the user mentions a principle by name (e.g., "check separation of concerns", "is this violating DRY?", "Law of Demeter", "KISS", "YAGNI", "resilience", "evolvability", "loose coupling"). Supports checking all ten principles at once or focusing on a single principle.
    0
    installs
  21. Explain System Tradeoffs · florianbuetow bundle
    This skill should be used when the user asks to "explain system tradeoffs", "analyze architecture tradeoffs", "what tradeoffs does this system make", "reverse-engineer design decisions", "audit distributed system design", or "explain the design choices in this codebase". Also triggers when the user mentions a tradeoff axis by name (e.g., "consistency vs availability", "latency vs throughput", "CAP theorem", "PACELC", "sharding tradeoffs", "resilience patterns", "data distribution strategy"). Supports analyzing all six axes at once or focusing on a single axis.
    0
    installs