Kranz Services

Use existing Kranz runtimes via MCP to inspect services, logs, ports, actions, and plans, or to start, stop, restart, and handle confirmation tokens. Also use before starting a dev server, worker, Docker stack, build, test, or migration. If no matching runtime exists, use the project's normal workflow.

62 stars 2 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add kranz-org/kranz --skill kranz-services

Manual install

git clone --depth 1 https://github.com/kranz-org/kranz.git /tmp/kranz
mkdir -p ~/.claude/skills
cp -r /tmp/kranz/skills/kranz-services ~/.claude/skills/kranz-services

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Work with services through Kranz

Kranz is a local service orchestrator. A developer may already have the project
running before the task starts, and that runtime should remain intact after the
task finishes. Starting another `npm run dev`, worker, or Docker stack can create
a duplicate process with unrelated logs and ports.

Prefer Kranz MCP tools over shell commands when they are available. MCP is
already connected to the runtime API and does not require direct access to its
Unix socket.

## Discover the runtime first

Inspect the complete tool registry, including lazy or deferred tools, for tools
named like `mcp__kranz__runtimes`, `mcp__kranz__status`, and
`mcp__kranz__logs`.

If `mcp__kranz__runtimes` is available:

1. Call it.
2. Select the runtime whose `directory` is equal to, or a parent of, the current
   working directory.
3. Pass its `name` as `runtime` to every runtime-scoped MCP call.

If Kranz MCP is unavailable or its transport cannot start, run exactly one
fallback discovery command:

```bash
kranz ps --output json
```

Match the current directory against `.data[].directory`, including parent
directories. If there is no matching runtime, stop applying this skill and use
the project's ordinary workflow. Do not infer Kranz usage from a configuration
file: personal Kranz configuration may live above the repository or outside
version control.

When a runtime is found, tell the user briefly that subsequent service work
will use it.

Read the full skill on GitHub

Details

Skill name: kranz-services
Repository: kranz-org/kranz
Path: skills/kranz-services/SKILL.md
License: MIT
Repo updated: 20 October 2026
Listed in: heilcheng/awesome-agent-skills

FAQ

What does the Kranz Services skill do?

How do I install the Kranz Services skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add kranz-org/kranz --skill kranz-services. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Kranz Services popular?

It lives in kranz-org/kranz, which has 62 GitHub stars and 2 forks, and is included in 1 curated skill list.

Related skills

Precoil Emt

David-Precoil/testing-business-ideas-with-claude

Use this skill when the user wants to test a business idea, strategy, or initiative against real-world risk. Triggers include: 'test my idea', 'what are the riskiest assumptions', 'help me validate this', 'run EMT on this', 'extract assumptions', 'assumption mapping', 'what could go wrong with this plan', 'pressure test this', 'validate this plan', 'what could go wrong with this strategy', 'identify hidden risk in this idea', or any request to pressure-test a business decision before committing resources. Runs a guided Extract → Map → Test system based on David J. Bland's Precoil methodology.

Testing & QA

Persona

takechanman1228/claude-persona

Build a persona panel, explore customer motivations through open-ended questions, and pressure-test product concepts before spending on fieldwork. Generates diverse AI persona panels, runs agent-separated interviews (qualitative ask or structured concept test), analyzes results with theme synthesis, cross-tabs, and charts, and delivers executive research reports. Use when the user wants to ask a panel about motivations or barriers, which concept to launch, who to target first, which message resonates, whether a value proposition works, or needs a reusable persona panel.

Testing & QAIn 2 lists

Playwright Browser

AndyShiu/claude-skill-playwright-browser

Headless, reproducible browser automation with Playwright for any project — screenshots of web pages or local dev servers (desktop/tablet/mobile, full page or one element, single page or every page/menu of an app in one batch), frontend audits (console errors, failed requests, broken images/links, responsive overflow, axe accessibility, LCP/CLS performance), before/after visual comparison, scripted E2E flows (log in, click, fill, page through, assert), and logged-in pages via saved sessions. Use this whenever the user wants to screenshot or visually check a site, find frontend bugs, see how a

Testing & QA12

Venice Responses

160

veniceai/skills

Use Venice's Alpha POST /responses endpoint - an OpenAI-compatible, stateless Responses API with typed output blocks (reasoning, message, function_call, web_search_call). Covers request shape, input items, tools (function, web_search, x_search), reasoning controls, incomplete responses, streaming events, differences from /chat/completions, the supported venice_parameters subset, and E2EE behavior.

Testing & QAIn 1 list27

Cypress Author

cypress-io/ai-toolkit

Creates, updates, and fixes Cypress tests (E2E/end-to-end and component tests). Use when the user asks to create tests, add tests, write tests, update tests, test this file/component, new spec, or fix a failing or flaky test. Apply even when the user does not say 'Cypress' (e.g. 'create tests for this file'). Prefer cypress-explain when the user only wants to explain or review tests without changing code.

Testing & QAIn 1 list

Clarify Intent and Establish Shared Understanding

206

Inference1/clarify-intent-and-establish-shared-understanding

Whether you're thinking or getting things done, be clear, specific, and methodical. Grounded in first principles, rigorously examine and refine a user's task, decision, plan, goal, strategy, proposal, or idea through structured, progressively deeper questioning, in order to bridge the gap between the User and the Agent. Use when the user explicitly requests grilling, challenge, pressure-testing, cross-examination, red-team review, pre-mortem analysis, or a decision audit. The goal is to uncover unclear objectives, hidden assumptions, contradictions, weak evidence, missing information, overlook

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.