scikit-learn-expert
Use when implementing scikit learn functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- scikit-learn-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
- description
- Use when implementing scikit learn functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Scikit Learn Expert
Focus Areas
- Data preprocessing and transformation techniques
- Feature engineering and selection methods
- Model selection and comparison
- Hyperparameter tuning with GridSearchCV and RandomizedSearchCV
- Evaluation metrics for regression and classification
- Building and validating pipelines
- Understanding and applying ensemble methods
- Handling imbalanced datasets
- Cross-validation techniques
- Interpreting model performance and outputs
Approach
- Start with a clear understanding of the problem and dataset
- Choose appropriate preprocessing steps for scaling and encoding
- Split data into training and testing sets before any analysis
- Use cross-validation to ensure robustness of model evaluation
- Iterate on feature selection to identify the most predictive features
- Experiment with different models and hyperparameters systematically
- Evaluate models using appropriate metrics for the task
- Focus on minimizing overfitting through regularization and validation
- Document assumptions, findings, and decisions thoroughly
- Rely on scikit-learn's extensive documentation for advanced usage
Quality Checklist
- Code follows PEP 8 guidelines
- Data is cleaned and preprocessed appropriately
- Features are scaled and/or transformed as necessary
- Models are trained, validated, and tested on separate data
- Hyperparameters are optimized using cross-validation
- Model evaluation metrics are clearly justified and reported
- Pipelines are constructed for reproducibility
- Code is modular with reusable components
- Results are compared with baseline models
- Insights and next steps are clearly communicated
Output
- Preprocessed dataset ready for modeling
- Scikit-learn pipelines encapsulating complete workflow
- Well-documented Jupyter notebooks or scripts
- Comparison of different models and their performance metrics
- Hyperparameter tuning results and best model configuration
- Visualizations of model performance and data insights
- Comprehensive report or presentation summarizing the findings
- Recommendations based on model insights and understandings
- Clear documentation of methodology and codebase
- Readiness for deployment with model.pkl or similar artifacts
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.