thomasholknielsen
27 verified skills78 total stars
websearch-standard
Standard multi-source verification search strategy for moderate complexity research. 2-iteration workflow with source ranking, consensus identification, and citation transparency. Use for feature comparisons, moderate complexity topics, fact-checking. Keywords: compare, differences, features, fact-check, verify, what are.
development6
json-formatter
Formats and validates JSON data. Use when you need to pretty-print JSON, fix formatting issues, or validate JSON syntax. ALWAYS USE THIS when doing JSON Formatting
development6
websearch-deep
ChatGPT-style deep research strategy with problem decomposition, multi-query generation (3-5 variations per sub-question), evidence synthesis with source ranking, numbered citations, and iterative refinement. Use for complex architecture decisions, multi-domain synthesis, strategic comparisons, technology selection. Keywords: architecture, integration, best practices, strategy, recommendations, comparison.
development6
skill-name
Explain what this skill does and when Claude should use it. Include trigger keywords and use cases.
data-ai6
azure-devops
Provides expert guidance on Azure DevOps tasks including work item management, pipelines, repositories, pull requests, and CI/CD workflows. Use when working with Azure DevOps projects, configuring pipelines, managing work items, or integrating Azure DevOps with development workflows.
development6
websearch-quick
Fast, targeted single-pass search strategy for simple factual lookups. 1-iteration workflow with authoritative source verification and minimal citations. Use for version lookups, documentation finding, simple definitions, existence checks. Keywords: what version, find docs, link to, what is, does X support.
development6
claude-tweaks:browse
Use for browser automation via agent-browser — defines session naming, screenshot/trace paths, and operation vocabulary used by /stories, /visual-review, and /review. Keywords - browse, browser, agent-browser, screenshot, scrape, automation.
tools2
claude-tweaks:challenge
Use when you need to challenge assumptions and remove bias from a problem statement before brainstorming. Takes an INBOX item or topic and produces a debiased problem framing.
data-ai2
claude-tweaks:version
Use when you want to know which version of the claude-tweaks plugin is installed.
tools2
claude-tweaks:wrap-up
Use when /claude-tweaks:review passes and you need to capture learnings, clean up specs/plans, update skills, and decide next steps. The lifecycle closure step.
testing2
claude-tweaks:stories
Use when generating or updating user story YAML files for UI testing — browses a site with agent-browser, discovers flows, creates structured stories using semantic locators (schema v2) with diff-aware updates, negative testing, source-aware contracts, journey awareness, and self-validation. Keywords - stories, generate, create, user journey, persona, QA, testing, semantic-locators.
testing2
claude-tweaks:design
Use when a lifecycle skill (/test, /review, /build, /flow, /visual-review, /specify) needs to invoke Impeccable design-quality commands. Wrapper that encapsulates "when, how, and whether to invoke Impeccable" so caller skills don't have to know.
development2
claude-tweaks:research
Use when conducting in-depth web research — multi-source synthesis, citation-audited reports with 4 runtime modes from quick (~2-5 min) to ultradeep (~20-45 min, multi-persona red-team). Keywords - research, deep research, web research, sources, citations, literature review.
development2
claude-tweaks:simplify
Use when you want to simplify recently changed code — catches unnecessary complexity from iterative development, verbose debugging patterns, and cross-file inconsistencies. Works standalone or as a step within /claude-tweaks:build and /claude-tweaks:review.
development2
claude-tweaks:tidy
Use when the backlog needs hygiene — review stale INBOX items, partially-complete specs, orphaned plans, and overall spec health
tools2
claude-tweaks:test
Use when you need to run verification checks (types, lint, tests) or validate QA stories — the mechanical "does it work?" gate.
development2
claude-tweaks:init
Use when initializing the workflow system for a project — bootstraps structure, analyzes the codebase, generates CLAUDE.md with adaptive philosophy, skills, and rules. Re-run to find drift, gaps, and stale configuration.
development2
claude-tweaks:build
Use when implementing a spec or design doc end-to-end. Accepts a spec number for full lifecycle tracking, or a design doc path to skip /claude-tweaks:specify and build directly from brainstorming output.
development2
claude-tweaks:capture
Use when capturing ideas that need specification later — brain dumps, half-formed features, things to not forget
testing2
claude-tweaks:flow
Use when you want to run an automated build → test → review → polish → wrap-up pipeline on a spec without stopping between steps. Accepts specs only — design docs must be decomposed via /claude-tweaks:specify first.
development2
claude-tweaks:journeys
Use when you want to create or update user journey documentation for recently built features. Works standalone or as a step within /claude-tweaks:build.
development2
claude-tweaks:help
Use when you need a quick reference for available commands, want to see workflow status, or need a recommendation for what to do next.
data-ai2
claude-tweaks:specify
Use when converting a brainstorming design document into agent-sized work units (specs). Takes a design doc and decomposes it into self-contained specifications.
testing2
claude-tweaks:reflect
Use when you want to step back and evaluate recent work through structured lenses — approach correctness, structural debt, surprises, near-misses. Works standalone or as a step within /claude-tweaks:review and /claude-tweaks:wrap-up.
tools2
claude-tweaks:review
Use when a build is complete and you need analytical judgment on code quality, correctness, and simplicity before wrapping up. Gates on /claude-tweaks:test passing. The quality gate between implementation and lifecycle cleanup.
development2
claude-tweaks:ledger
Use when you need to create, update, query, or resolve open items in a pipeline ledger file. Called by /claude-tweaks:build, /claude-tweaks:test, /claude-tweaks:review, /claude-tweaks:wrap-up, and /claude-tweaks:flow — or standalone for ledger inspection.
development2
claude-tweaks:visual-review
Use when you want to visually review a running application in the browser — inspect UI quality, walk user journeys, discover undocumented journeys, or generate creative improvement ideas. Works standalone or as a step within /claude-tweaks:review.
testing2