Agent skill
csv-workbench
Analyze CSV files in /mnt/data and return concise numeric summaries.
Install this agent skill to your Project
npx add-skill https://github.com/openai/openai-agents-python/tree/main/examples/tools/skills/csv-workbench
SKILL.md
CSV Workbench
Use this skill when the user asks for quick analysis of tabular data.
Workflow
- Inspect the CSV schema first (
head,python csv.DictReader, or both). - Compute requested aggregates with a short Python script.
- Return concise results with concrete numbers and units when available.
Constraints
- Prefer Python stdlib for portability.
- If data is missing or malformed, state assumptions clearly.
- Keep the final answer short and actionable.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
openai-knowledge
Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.
final-release-review
Perform a release-readiness review by locating the previous release tag from remote tags and auditing the diff (e.g., v1.2.3...<commit>) for breaking changes, regressions, improvement opportunities, and risks before releasing openai-agents-python.
examples-auto-run
Run python examples in auto mode with logging, rerun helpers, and background control.
implementation-strategy
Decide how to implement runtime and API changes in openai-agents-python before editing code. Use when a task changes exported APIs, runtime behavior, serialized state, tests, or docs and you need to choose the compatibility boundary, whether shims or migrations are warranted, and when unreleased interfaces can be rewritten directly.
docs-sync
Analyze main branch implementation and configuration to find missing, incorrect, or outdated documentation in docs/. Use when asked to audit doc coverage, sync docs with code, or propose doc updates/structure changes. Only update English docs under docs/** and never touch translated docs under docs/ja, docs/ko, or docs/zh. Provide a report and ask for approval before editing docs.
runtime-behavior-probe
Plan and execute runtime-behavior investigations with temporary probe scripts, validation matrices, state controls, and findings-first reports. Use only when the user explicitly invokes this skill to verify actual runtime behavior beyond normal code-level checks, especially to uncover edge cases, undocumented behavior, or common failure modes in local or live integrations. A baseline smoke check is fine as an entry point, but do not stop at happy-path confirmation.
Didn't find tool you were looking for?