all publishers

florianbuetow

@florianbuetow source repo

131 published skills · page 2 of 2

  1. ▌
    Arc42 Framework · florianbuetow bundle
    Generate arc42 architecture documentation from a codebase. Read the repository into a structured evidence base, then author the 12 arc42 sections — emitting Mermaid diagrams where the code gives high-confidence structure, and explicit typed GAP flags where human input is needed, never fabricating. Use when asked to create, scaffold, or update arc42 docs, an architecture document, or per-section architecture views (building block view, runtime view, deployment view, etc.) for a project.
    21 repo stars
  2. ▌
    Clean Code · florianbuetow bundle
    This skill should be used when the user asks to "check clean code", "review code cleanliness", "find code smells", "is this function too long", "are these names clear", "review my error handling", "check my tests", or "clean up this code". Also triggers when the user mentions Clean Code, Uncle Bob, Robert Martin, meaningful names, function length, comment rot, F.I.R.S.T. tests, or names a dimension directly ("naming", "boundaries", "concurrency"). Supports auditing all nine dimensions at once or focusing on a single dimension.
    21 repo stars
  3. ▌
    Onboarding · florianbuetow
    This skill should be used when starting a new session, resuming work, or when the user asks to "onboard", "get oriented", "catch me up", "what's the state of the project", "what should I work on", or "where did we leave off". Gathers project context by reading instructions, checking git state, reviewing open issues, and identifying next steps.
    21 repo stars
  4. ▌
    Maptasks · florianbuetow bundle
    Use when you have a specified engineering task or task list and need to decide which AI model should handle each work unit — routes tasks across Claude Opus/Sonnet/Haiku, GPT-5.4 family, GPT-5.3-Codex, and Gemini 2.5/3 with per-unit category, evidence-based rationale, context briefing, and failure-mode warnings. Also checks whether the task is broken down enough and proposes finer decomposition before routing.
    21 repo stars
  5. ▌
    Sessionlog Export All · florianbuetow
    This skill should be used when the user asks to "export all sessions", "export all session logs", "batch export sessions", "sessionlog export-all", "convert all sessions", or wants to export every Claude Code session for the current project as standard LLM conversation JSON and TXT files.
    21 repo stars
  6. ▌
    Sessionlog Tokenusage · florianbuetow
    This skill should be used when the user asks to "show token usage", "how many tokens", "token count", "token stats", "input output tokens", "API usage", "usage summary", "sessionlog tokenusage", "tokenusage", or wants to extract and report input/output token counts from Claude Code session logs.
    21 repo stars
  7. ▌
    Data Disclosure · florianbuetow
    This skill should be used when the user asks to "check for personal data disclosure", "analyze PII exposure", "find privacy issues related to data leakage", "check for unauthorized data sharing", or mentions "disclosure" in a privacy context. Maps to LINDDUN category D2. Focuses specifically on PERSONAL data disclosure, complementing STRIDE information disclosure.
    21 repo stars
  8. ▌
    Info Disclosure · florianbuetow
    This skill should be used when the user asks to "check for information disclosure", "analyze data leakage risks", "find data exposure vulnerabilities", or mentions "information disclosure" in a security context. Maps to STRIDE category I.
    21 repo stars
  9. ▌
    Insecure Design · florianbuetow bundle
    This skill should be used when the user asks to "check for design flaws", "analyze security design", "find insecure design patterns", "review threat model", "check business logic security", "find missing security controls", or mentions "insecure design" in a security context. Maps to OWASP Top 10 2021 A04:2021 - Insecure Design.
    21 repo stars
  10. ▌
    Pasta Decompose · florianbuetow
    This skill should be used when the user asks to "decompose the application", "map trust boundaries", "identify components and roles", "catalog permissions", or is running PASTA stage 3. Also triggers when the user asks about role-based access control mapping, data classification, or service-to-service trust in a threat modeling context. Part of the PASTA threat modeling methodology (Stage 3 of 7).
    21 repo stars
  11. ▌
    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.
    21 repo stars
  12. ▌
    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.
    21 repo stars
  13. ▌
    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).
    21 repo stars
  14. ▌
    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).
    21 repo stars
  15. ▌
    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.
    21 repo stars
  16. ▌
    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.
    21 repo stars
  17. ▌
    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.
    21 repo stars
  18. ▌
    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.
    21 repo stars
  19. ▌
    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.
    21 repo stars
  20. ▌
    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.
    21 repo stars
  21. ▌
    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.
    21 repo stars
  22. ▌
    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.
    21 repo stars
  23. ▌
    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.
    21 repo stars
  24. ▌
    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.
    21 repo stars
  25. ▌
    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.
    21 repo stars
  26. ▌
    Context Research · florianbuetow
    <!--
    21 repo stars
  27. ▌
    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.
    21 repo stars
  28. ▌
    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.
    21 repo stars
  29. ▌
    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.
    21 repo stars
  30. ▌
    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.
    21 repo stars
  31. ▌
    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.
    21 repo stars