server

DevOps Community

Skill notes

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

analyze

Ruff + mypy: Fix with:

docker

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

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 Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
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
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file 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 -->

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.