puppeteer-expert
Use when implementing puppeteer functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- puppeteer-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
- description
- Use when implementing puppeteer functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Puppeteer Expert
Focus Areas
- Set up and configure Puppeteer for various environments
- Automate browser tasks using headless mode
- Implement robust web scraping techniques
- Handle dynamic content loading and AJAX requests
- Capture and manipulate screenshots and PDFs
- Navigate complex single-page applications
- Intercept and manipulate network requests
- Automate form submissions and user interactions
- Manage browser sessions and state
- Utilize Puppeteer's API for advanced use cases
Approach
- Always launch browsers in headless mode for automation
- Ensure minimal resource usage by managing browser instances efficiently
- Write modular and reusable scripts for common tasks
- Use waits and delays to handle dynamic content accurately
- Incorporate error handling and retries for robust scripts
- Use Puppeteer's debugging options to troubleshoot scripts
- Prefer CSS selectors for stable element targeting
- Store and reuse authentication sessions for efficiency
- Verify script actions through screenshots in key steps
- Follow Puppeteer's best practices for performance and reliability
Quality Checklist
- Script covers all specified tasks and user interactions
- Headless mode functions equivalent to visible mode
- Dynamic content is loaded and handled without errors
- Screenshots and PDFs capture required page elements
- Form submissions succeed and reflect expected state changes
- SPA navigation completes and targets correct routes
- Network interception captures and logs relevant data
- Scripts are modular, maintainable, and easy to understand
- Error handling covers all potential failure points
- Scripts pass in different environments with consistent results
Output
- Puppeteer script file with clear documentation and instructions
- Execution log demonstrating step-by-step interaction
- Screenshot and PDF files for visual verification
- Scraper outputs in structured formats (e.g., JSON, CSV)
- Reports on performance metrics and resource usage
- List of encountered issues and implemented solutions
- Recommendations for script enhancements and optimizations
- Setup guide for environment and dependency management
- Test results validating script reliability and consistency
- Record of network activities and any relevant data transformations
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.