dig
Look up documentation and source code for libraries and packages. Use when the user asks a question about a library, needs to understand a library's API, or when you need information about a library t
SKILL.mdDataset/Skills/malware/dig/SKILL.md
GitHubDig
Look up library documentation by finding and exploring the library's source code repository.
Overview
The Dig skill serves as a comprehensive research assistant that enables thorough exploration of software libraries and packages. When users encounter unfamiliar tools or need deeper understanding of existing implementations, this skill orchestrates the discovery and analysis process.
The primary objective is to locate relevant documentation and source code repositories, then synthesize findings into actionable insights. This capability is particularly valuable when users ask questions about library usage patterns, API structures, or implementation details that are not immediately apparent from surface-level documentation.
Usage
To utilize the Dig skill effectively, users should pose questions related to library exploration, API understanding, or implementation guidance. The skill automatically triggers when encountering queries such as "How do I integrate X library into my workflow?", "What are the key APIs available in Y?", or "Demonstrate how Z library manages data persistence."
The workflow begins with checking for local availability of library resources, followed by repository cloning when necessary. A Research agent is then launched to traverse the repository structure and extract relevant information to address the user's inquiry.
Guidelines
Operational procedures for the Dig skill are outlined below to ensure consistent and effective library research:
Repository Management
Maintain a standardized repository location at /tmp/cc-repos/ for all cloned libraries. This central storage facilitates efficient access and reduces redundant cloning operations.
Research Agent Configuration
When initiating repository exploration, configure the Research agent with the Explore subagent type to enable comprehensive traversal capabilities. The agent should focus on documentation files, source code architecture, API interfaces, and usage examples.
Quality Assurance
Ensure all research outputs include clear documentation of findings, with emphasis on practical application examples and implementation recommendations. Regular validation of repository contents against current best practices maintains the relevance and accuracy of delivered insights.
Examples
Library Discovery Scenario
When investigating a new Python package, the agent would:
- Search for the package's GitHub repository and verify its documentation completeness
- Clone the repository to the standard location for detailed analysis
- Launch the Research agent to examine the package's API structure and usage patterns
- Synthesize findings into a comprehensive report with actionable recommendations
API Documentation Review
For API-focused inquiries, the agent examines:
- Public interface definitions and export structures
- Documentation files including README and API references
- Example implementations demonstrating practical usage
- Test suites validating functionality and reliability
Integration Guidance
The skill provides guidance on integrating libraries into existing workflows, including:
- Compatibility considerations with current technology stacks
- Configuration requirements and customization options
- Performance optimization strategies for production environments
- Maintenance procedures for ongoing library evolution