server

DevOps Community

Repo stars 0
Author repo skills-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Test, analyze, or start Docker for the server project Use when this capability is needed. commands below if your server shortnam…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Server”, “Actions”, “test”, “analyze”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name server directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Server / Actions / test” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Server

Arguments: $ARGUMENTS

Path: resolve from ~/.claude/project-repos.json using shortname server. The example registry ships a Python / FastAPI project; adjust the commands below if your server shortname points at a different stack.

All commands assume uv is installed. If the project uses a different runner (poetry, pip, docker compose exec), update projects/server.md and this file together.

Actions

`test`

# All tests:
cd {server-path} && uv run pytest

# Specific file:
cd {server-path} && uv run pytest tests/{path}.py

# Filter (substring match on test id):
cd {server-path} && uv run pytest -k "{filter}"

# With coverage:
cd {server-path} && uv run pytest --cov=app --cov-report=term

`analyze`

Ruff + mypy:

cd {server-path} && uv run ruff check .
cd {server-path} && uv run ruff format --check .
cd {server-path} && uv run mypy app

Fix with:

cd {server-path} && uv run ruff check --fix .
cd {server-path} && uv run ruff format .

`docker`

If the project ships a docker-compose.yml for local dev (Postgres, Redis, LocalStack, etc.):

cd {server-path} && docker compose up -d

Migrations (example with Alembic):

cd {server-path} && uv run alembic upgrade head

Process

Parse arguments: action (test / analyze / docker), optional test filter
If docker action and containers aren't running, start them first
Run the command
Report result (summary of passed/failed, or first analyzer errors)

Source: ajvelo/claude-toolkit — distributed by TomeVault.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: DevOps
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @tomevault-io · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Manual integration
External API key: No requirement detected
Detected OS requirements: Docker
Runtime requirements: Python · Docker
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview server.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

## Server

**Arguments:** $ARGUMENTS

**Path:** resolve from `~/.claude/project-repos.json` using shortname
`server`. The example registry ships a Python / FastAPI project; adjust the
commands below if your `server` shortname points at a different stack.

All commands assume `uv` is installed. If the project uses a different
runner (poetry, pip, docker compose exec), update `projects/server.md` and
this file together.

## Actions

### `test`

```bash
# All tests:
cd {server-path} && uv run pytest

# Specific file:
cd {server-path} && uv run pytest tests/{path}.py

# Filter (substring match on test id):
cd {server-path} && uv run pytest -k "{filter}"

# With coverage:
cd {server-path} && uv run pytest --cov=app --cov-report=term
```

### `analyze`

Ruff + mypy:
```bash
cd {server-path} && uv run ruff check .
cd {server-path} && uv run ruff format --check .
cd {server-path} && uv run mypy app
```

Fix with:
```bash
cd {server-path} && uv run ruff check --fix .
cd {server-path} && uv run ruff format .
```

### `docker`

If the project ships a `docker-compose.yml` for local dev (Postgres, Redis,
LocalStack, etc.):

```bash
cd {server-path} && docker compose up -d
```

Migrations (example with Alembic):
```bash
cd {server-path} && uv run alembic upgrade head
```

## Process

1. Parse arguments: action (`test` / `analyze` / `docker`), optional test filter
2. If `docker` action and containers aren't running, start them first
3. Run the command
4. Report result (summary of passed/failed, or first analyzer errors)

---
> Source: [ajvelo/claude-toolkit](https://github.com/ajvelo/claude-toolkit) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Server → Actions → test → analyze → docker → Process
terms    -> Arguments · Path · Path: resolve from ~/.claude/project-repos.json using shortname server. · All commands assume uv is installed. · Ruff + mypy: bash cd {server-path} && uv run ruff check . · Fix with: bash cd {server-path} && uv run ruff check --fix . · 1. Parse arguments: action (test / analyze / docker), optional test filter 2. · --- > Source: [ajvelo/claude-toolkit](https://github.com/ajvelo/claude-toolkit) — distributed by [TomeVault](https://tomevault.io).
files/cmd -> ~/.claude/project-repos.json · server · projects/server.md · test · analyze · docker · docker-compose.yml
body sha256 -> cc591f374101