Agent skill
example-data-processor
Process CSV data files by cleaning, transforming, and analyzing them. Use this when users need to work with CSV files, clean data, or perform basic data analysis tasks.
Install this agent skill to your Project
npx add-skill https://github.com/fkesheh/skill-mcp/tree/main/example-skill
SKILL.md
Example Data Processor
This skill demonstrates a complete skill structure with scripts, references, and proper documentation.
What This Skill Does
Processes CSV data files with these capabilities:
- Clean and validate data
- Transform columns
- Generate summary statistics
- Export results
Usage
Process a CSV file
To process a CSV file:
Process the data in myfile.csv
The skill will:
- Read the CSV file
- Clean the data (remove nulls, fix formats)
- Generate statistics
- Output a summary report
Custom Processing
For custom processing options:
Process sales.csv and group by region
Scripts
scripts/process_csv.py - Main data processing script
- Reads CSV files
- Applies transformations
- Generates output
scripts/fetch_data.py - API data fetcher (demonstrates uv dependencies)
- Fetches data from APIs using requests
- Beautiful output formatting with rich
- Auto-installs dependencies via uv inline metadata (PEP 723)
- No manual pip install needed!
scripts/validate.py - Data validation script
- Checks data quality
- Reports issues
Configuration
The scripts use these environment variables:
OUTPUT_DIR- Where to save processed files (optional)MAX_ROWS- Maximum rows to process (optional)
Set them using:
Set OUTPUT_DIR to /path/to/output
Reference Documentation
For detailed information:
- Data Formats - Supported data formats and schemas
- Examples - Common usage examples
Troubleshooting
"File not found" error:
- Ensure the CSV file exists
- Provide the full path to the file
"Invalid data" error:
- Check the CSV format matches expected schema
- See Data Formats for requirements
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
every-style-editor
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
manage-codex
Autonomous Codex batch orchestrator. Use for "/manage-codex", "manage codex", "use codex", "dispatch to codex", or long-running Codex work.
seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
capture-learning
Analyze recent conversation context and capture learnings to project knowledge files (for project-specific insights) or skills/commands/subagents (for cross-project patterns). Use when the user asks to "capture this learning", "update the docs with this", "remember this for next time", "document this issue", "add this to CLAUDE.md", "save this knowledge", or "update project knowledge". Also triggers after resolving build/setup issues, discovering non-obvious patterns, or completing debugging sessions with valuable insights.
agent-changelog
Compile an agent-optimized changelog by cross-referencing git history with plans and documentation. Use when asked to "update changelog", "compile history", "document project evolution", or proactively after major milestones, architectural changes, or when stale/deprecated information is detected that could confuse coding agents.
Didn't find tool you were looking for?