server
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- DevOps
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- 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
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: server
description: Test, analyze, or start Docker for the server project Use when this capability is needed. comman…
category: devops
runtime: Python / Docker
---
# server output preview
## PART A: Task fit
- Use case: Test, analyze, or start Docker for the server project Use when this capability is needed. commands below if your server shortname points at a different stack. All commands assume uv is installed. If the project uses a different runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Server / Actions / test” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Test, analyze, or start Docker for the server project Use when this capability is needed. commands below if your server shortname points at a different stack. All commands assume uv is installed. If the project uses a different runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Server / Actions / test” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Server / Actions / test”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: server
description: Test, analyze, or start Docker for the server project Use when this capability is needed. comman…
category: devops
source: tomevault-io/skills-registry
---
# server
## When to use
- Test, analyze, or start Docker for the server project Use when this capability is needed. commands below if your serve…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Server / Actions / test” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "server" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Server / Actions / test
rules -> SKILL.md triggers / order / output contract
runtime -> Python / Docker | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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=termanalyze
Ruff + mypy:
cd {server-path} && uv run ruff check .
cd {server-path} && uv run ruff format --check .
cd {server-path} && uv run mypy appFix 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 -dMigrations (example with Alembic):
cd {server-path} && uv run alembic upgrade headProcess
- Parse arguments: action (
test/analyze/docker), optional test filter - If
dockeraction 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.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review