028 Agents 1bbd0b4d

Name: 028 Agents 1bbd0b4d
Author: tools-only

ASecurity

- `evalview/`: Python package and CLI (`cli.py`). Modules: `adapters/` (framework integrations), `core/` (types, loader, pricing), `evaluators/` (cost, latency, output, sequence), `reporters/` (console, JSON). - `tests/`: Pytest assets and YAML scenarios under `tests/test-cases/*.yaml`. - `docs/`: Reference docs (adapters, database, backend setup). `examples/`: Example YAML and backend notes. - Root tooling: `Makefile`, `pyproject.toml`, `requirements.txt`, optional Node workspace (`package.json

9 stars
0 votes
0 copies
0 views
Added October 11, 2026

developmentpythonnodetestinggitapidatabasebackendsecurity

Works with

terminal
cli
api

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 028-agents_1bbd0b4d --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 028 Agents 1bbd0b4d?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 028 Agents 1bbd0b4d

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-028-agents-1bbd0b4d/badge)](https://www.skillsdirectory.com/skills/tools-only-028-agents-1bbd0b4d)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md

# Repository Guidelines

## Project Structure & Module Organization
- `evalview/`: Python package and CLI (`cli.py`). Modules: `adapters/` (framework integrations), `core/` (types, loader, pricing), `evaluators/` (cost, latency, output, sequence), `reporters/` (console, JSON).
- `tests/`: Pytest assets and YAML scenarios under `tests/test-cases/*.yaml`.
- `docs/`: Reference docs (adapters, database, backend setup). `examples/`: Example YAML and backend notes.
- Root tooling: `Makefile`, `pyproject.toml`, `requirements.txt`, optional Node workspace (`package.json`).

## Build, Test, and Development Commands
- Install: `make install` (editable) or `make dev-install` (adds dev deps).
- Quality: `make format` (black), `make lint` (ruff), `make typecheck` (mypy), `make check` (all).
- Tests: `make test` (pytest -v) or `make test-cov` (coverage HTML + terminal).
- Run example flow: `make run-example` (initializes `.evalview/` then runs sample case if present).
- CLI test runner: `evalview run [--pattern "*.yaml"] [--verbose]`.

## Coding Style & Naming Conventions
- Python 3.9+. Formatting via black (line length 100); lint with ruff; strict typing with mypy.
- Indentation: 4 spaces. Naming: modules/files `snake_case.py`, classes `PascalCase`, functions/vars `snake_case`.
- Keep public CLI/API stable; extend via new adapters/evaluators under existing folders.

## Testing Guidelines
- Framework: `pytest`. Place Python tests under `tests/`. Name files `test_*.py`.
- Scenario tests: add YAML cases to `tests/test-cases/` (see existing examples). Prefer precise `expected.output.contains` and realistic thresholds (`max_cost`, `max_latency`).
- Run locally with `pytest` or `evalview run --pattern "<case>.yaml" --verbose`.

## Commit & Pull Request Guidelines
- Commits: imperative, concise, and scoped (e.g., "Add LangGraph adapter config"). Group related changes; include rationale when behavior changes.
- PRs: clear description, linked issues, reproduction/testing steps, CLI output or screenshots when useful. Update docs/tests as needed.
- Checks: ensure `make check` and `make test` pass; avoid committing secrets or `.env.local`.

## Security & Configuration Tips
- Secrets: store in `.env.local` (gitignored). Common: `OPENAI_API_KEY`, service endpoints.
- Local config: `.evalview/config.yaml` controls defaults for runs. Avoid hard‑coding credentials in tests or examples.