[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFFDHS7R7E6QSEGE0556S3":3,"skill-same:01M6AFFDHS7R7E6QSEGE0556S3":100},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6AFFDHS7R7E6QSEGE0556S3","labarchive-integration",null,"Electronic lab notebook API integration. Access notebooks, manage entries\u002Fattachments, backup notebooks, integrate with Protocols.io\u002FJupyter\u002FREDCap, for programmatic ELN workflows.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Flabarchive-integration\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"integration","labarchive integration","integrate","for","lab","programmatic","with","io","entries","notebook","api integration","manage","workflows","jupyter","access","api","backup","attachments","protocols","2026-11-10 10:12:30",false,"---\nname: labarchive-integration\ndescription: \"Electronic lab notebook API integration. Access notebooks, manage entries\u002Fattachments, backup notebooks, integrate with Protocols.io\u002FJupyter\u002FREDCap, for programmatic ELN workflows.\"\n---\n\n# LabArchives Integration\n\n## Overview\n\nLabArchives is an electronic lab notebook platform for research documentation and data management. Access notebooks, manage entries and attachments, generate reports, and integrate with third-party tools programmatically via REST API.\n\n## When to Use This Skill\n\nThis skill should be used when:\n- Working with LabArchives REST API for notebook automation\n- Backing up notebooks programmatically\n- Creating or managing notebook entries and attachments\n- Generating site reports and analytics\n- Integrating LabArchives with third-party tools (Protocols.io, Jupyter, REDCap)\n- Automating data upload to electronic lab notebooks\n- Managing user access and permissions programmatically\n\n## Core Capabilities\n\n### 1. Authentication and Configuration\n\nSet up API access credentials and regional endpoints for LabArchives API integration.\n\n**Prerequisites:**\n- Enterprise LabArchives license with API access enabled\n- API access key ID and password from LabArchives administrator\n- User authentication credentials (email and external applications password)\n\n**Configuration setup:**\n\nUse the `scripts\u002Fsetup_config.py` script to create a configuration file:\n\n```bash\npython3 scripts\u002Fsetup_config.py\n```\n\nThis creates a `config.yaml` file with the following structure:\n\n```yaml\napi_url: https:\u002F\u002Fapi.labarchives.com\u002Fapi  # or regional endpoint\naccess_key_id: YOUR_ACCESS_KEY_ID\naccess_password: YOUR_ACCESS_PASSWORD\n```\n\n**Regional API endpoints:**\n- US\u002FInternational: `https:\u002F\u002Fapi.labarchives.com\u002Fapi`\n- Australia: `https:\u002F\u002Fauapi.labarchives.com\u002Fapi`\n- UK: `https:\u002F\u002Fukapi.labarchives.com\u002Fapi`\n\nFor detailed authentication instructions and troubleshooting, refer to `references\u002Fauthentication_guide.md`.\n\n### 2. User Information Retrieval\n\nObtain user ID (UID) and access information required for subsequent API operations.\n\n**Workflow:**\n\n1. Call the `users\u002Fuser_access_info` API method with login credentials\n2. Parse the XML\u002FJSON response to extract the user ID (UID)\n3. Use the UID to retrieve detailed user information via `users\u002Fuser_info_via_id`\n\n**Example using Python wrapper:**\n\n```python\nfrom labarchivespy.client import Client\n\n# Initialize client\nclient = Client(api_url, access_key_id, access_password)\n\n# Get user access info\nlogin_params = {'login_or_email': user_email, 'password': auth_token}\nresponse = client.make_call('users', 'user_access_info', params=login_params)\n\n# Extract UID from response\nimport xml.etree.ElementTree as ET\nuid = ET.fromstring(response.content)[0].text\n\n# Get detailed user info\nparams = {'uid': uid}\nuser_info = client.make_call('users', 'user_info_via_id', params=params)\n```\n\n### 3. Notebook Operations\n\nManage notebook access, backup, and metadata retrieval.\n\n**Key operations:**\n\n- **List notebooks:** Retrieve all notebooks accessible to a user\n- **Backup notebooks:** Download complete notebook data with optional attachment inclusion\n- **Get notebook IDs:** Retrieve institution-defined notebook identifiers for integration with grants\u002Fproject management systems\n- **Get notebook members:** List all users with access to a specific notebook\n- **Get notebook settings:** Retrieve configuration and permissions for notebooks\n\n**Notebook backup example:**\n\nUse the `scripts\u002Fnotebook_operations.py` script:\n\n```bash\n# Backup with attachments (default, creates 7z archive)\npython3 scripts\u002Fnotebook_operations.py backup --uid USER_ID --nbid NOTEBOOK_ID\n\n# Backup without attachments, JSON format\npython3 scripts\u002Fnotebook_operations.py backup --uid USER_ID --nbid NOTEBOOK_ID --json --no-attachments\n```\n\n**API endpoint format:**\n```\nhttps:\u002F\u002F\u003Capi_url>\u002Fnotebooks\u002Fnotebook_backup?uid=\u003CUID>&nbid=\u003CNOTEBOOK_ID>&json=true&no_attachments=false\n```\n\nFor comprehensive API method documentation, refer to `references\u002Fapi_reference.md`.\n\n### 4. Entry and Attachment Management\n\nCreate, modify, and manage notebook entries and file attachments.\n\n**Entry operations:**\n- Create new entries in notebooks\n- Add comments to existing entries\n- Create entry parts\u002Fcomponents\n- Upload file attachments to entries\n\n**Attachment workflow:**\n\nUse the `scripts\u002Fentry_operations.py` script:\n\n```bash\n# Upload attachment to an entry\npython3 scripts\u002Fentry_operations.py upload --uid USER_ID --nbid NOTEBOOK_ID --entry-id ENTRY_ID --file \u002Fpath\u002Fto\u002Ffile.pdf\n\n# Create a new entry with text content\npython3 scripts\u002Fentry_operations.py create --uid USER_ID --nbid NOTEBOOK_ID --title \"Experiment Results\" --content \"Results from today's experiment...\"\n```\n\n**Supported file types:**\n- Documents (PDF, DOCX, TXT)\n- Images (PNG, JPG, TIFF)\n- Data files (CSV, XLSX, HDF5)\n- Scientific formats (CIF, MOL, PDB)\n- Archives (ZIP, 7Z)\n\n### 5. Site Reports and Analytics\n\nGenerate institutional reports on notebook usage, activity, and compliance (Enterprise feature).\n\n**Available reports:**\n- Detailed Usage Report: User activity metrics and engagement statistics\n- Detailed Notebook Report: Notebook metadata, member lists, and settings\n- PDF\u002FOffline Notebook Generation Report: Export tracking for compliance\n- Notebook Members Report: Access control and collaboration analytics\n- Notebook Settings Report: Configuration and permission auditing\n\n**Report generation:**\n\n```python\n# Generate detailed usage report\nresponse = client.make_call('site_reports', 'detailed_usage_report',\n                           params={'start_date': '2025-01-01', 'end_date': '2025-10-20'})\n```\n\n### 6. Third-Party Integrations\n\nLabArchives integrates with numerous scientific software platforms. This skill provides guidance on leveraging these integrations programmatically.\n\n**Supported integrations:**\n- **Protocols.io:** Export protocols directly to LabArchives notebooks\n- **GraphPad Prism:** Export analyses and figures (Version 8+)\n- **SnapGene:** Direct molecular biology workflow integration\n- **Geneious:** Bioinformatics analysis export\n- **Jupyter:** Embed Jupyter notebooks as entries\n- **REDCap:** Clinical data capture integration\n- **Qeios:** Research publishing platform\n- **SciSpace:** Literature management\n\n**OAuth authentication:**\nLabArchives now uses OAuth for all new integrations. Legacy integrations may use API key authentication.\n\nFor detailed integration setup instructions and use cases, refer to `references\u002Fintegrations.md`.\n\n## Common Workflows\n\n### Complete notebook backup workflow\n\n1. Authenticate and obtain user ID\n2. List all accessible notebooks\n3. Iterate through notebooks and backup each one\n4. Store backups with timestamp metadata\n\n```bash\n# Complete backup script\npython3 scripts\u002Fnotebook_operations.py backup-all --email user@example.edu --password AUTH_TOKEN\n```\n\n### Automated data upload workflow\n\n1. Authenticate with LabArchives API\n2. Identify target notebook and entry\n3. Upload experimental data files\n4. Add metadata comments to entries\n5. Generate activity report\n\n### Integration workflow example (Jupyter → LabArchives)\n\n1. Export Jupyter notebook to HTML or PDF\n2. Use entry_operations.py to upload to LabArchives\n3. Add comment with execution timestamp and environment info\n4. Tag entry for easy retrieval\n\n## Python Package Installation\n\nInstall the `labarchives-py` wrapper for simplified API access:\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fmcmero\u002Flabarchives-py\ncd labarchives-py\nuv pip install .\n```\n\nAlternatively, use direct HTTP requests via Python's `requests` library for custom implementations.\n\n## Best Practices\n\n1. **Rate limiting:** Implement appropriate delays between API calls to avoid throttling\n2. **Error handling:** Always wrap API calls in try-except blocks with appropriate logging\n3. **Authentication security:** Store credentials in environment variables or secure config files (never in code)\n4. **Backup verification:** After notebook backup, verify file integrity and completeness\n5. **Incremental operations:** For large notebooks, use pagination and batch processing\n6. **Regional endpoints:** Use the correct regional API endpoint for optimal performance\n\n## Troubleshooting\n\n**Common issues:**\n\n- **401 Unauthorized:** Verify access key ID and password are correct; check API access is enabled for your account\n- **404 Not Found:** Confirm notebook ID (nbid) exists and user has access permissions\n- **403 Forbidden:** Check user permissions for the requested operation\n- **Empty response:** Ensure required parameters (uid, nbid) are provided correctly\n- **Attachment upload failures:** Verify file size limits and format compatibility\n\nFor additional support, contact LabArchives at support@labarchives.com.\n\n## Resources\n\nThis skill includes bundled resources to support LabArchives API integration:\n\n### scripts\u002F\n\n- `setup_config.py`: Interactive configuration file generator for API credentials\n- `notebook_operations.py`: Utilities for listing, backing up, and managing notebooks\n- `entry_operations.py`: Tools for creating entries and uploading attachments\n\n### references\u002F\n\n- `api_reference.md`: Comprehensive API endpoint documentation with parameters and examples\n- `authentication_guide.md`: Detailed authentication setup and configuration instructions\n- `integrations.md`: Third-party integration setup guides and use cases\n","# LabArchives Integration\n\n## Overview\n\nLabArchives is an electronic lab notebook platform for research documentation and data management. Access notebooks, manage entries and attachments, generate reports, and integrate with third-party tools programmatically via REST API.\n\n## When to Use This Skill\n\nThis skill should be used when:\n- Working with LabArchives REST API for notebook automation\n- Backing up notebooks programmatically\n- Creating or managing notebook entries and attachments\n- Generating site reports and analytics\n- Integrating LabArchives with third-party tools (Protocols.io, Jupyter, REDCap)\n- Automating data upload to electronic lab notebooks\n- Managing user access and permissions programmatically\n\n## Core Capabilities\n\n### 1. Authentication and Configuration\n\nSet up API access credentials and regional endpoints for LabArchives API integration.\n\n**Prerequisites:**\n- Enterprise LabArchives license with API access enabled\n- API access key ID and password from LabArchives administrator\n- User authentication credentials (email and external applications password)\n\n**Configuration setup:**\n\nUse the `scripts\u002Fsetup_config.py` script to create a configuration file:\n\n```bash\npython3 scripts\u002Fsetup_config.py\n```\n\nThis creates a `config.yaml` file with the following structure:\n\n```yaml\napi_url: https:\u002F\u002Fapi.labarchives.com\u002Fapi  # or regional endpoint\naccess_key_id: YOUR_ACCESS_KEY_ID\naccess_password: YOUR_ACCESS_PASSWORD\n```\n\n**Regional API endpoints:**\n- US\u002FInternational: `https:\u002F\u002Fapi.labarchives.com\u002Fapi`\n- Australia: `https:\u002F\u002Fauapi.labarchives.com\u002Fapi`\n- UK: `https:\u002F\u002Fukapi.labarchives.com\u002Fapi`\n\nFor detailed authentication instructions and troubleshooting, refer to `references\u002Fauthentication_guide.md`.\n\n### 2. User Information Retrieval\n\nObtain user ID (UID) and access information required for subsequent API operations.\n\n**Workflow:**\n\n1. Call the `users\u002Fuser_access_info` API method with login credentials\n2. Parse the XML\u002FJSON response to extract the user ID (UID)\n3. Use the UID to retrieve detailed user information via `users\u002Fuser_info_via_id`\n\n**Example using Python wrapper:**\n\n```python\nfrom labarchivespy.client import Client\n\n# Initialize client\nclient = Client(api_url, access_key_id, access_password)\n\n# Get user access info\nlogin_params = {'login_or_email': user_email, 'password': auth_token}\nresponse = client.make_call('users', 'user_access_info', params=login_params)\n\n# Extract UID from response\nimport xml.etree.ElementTree as ET\nuid = ET.fromstring(response.content)[0].text\n\n# Get detailed user info\nparams = {'uid': uid}\nuser_info = client.make_call('users', 'user_info_via_id', params=params)\n```\n\n### 3. Notebook Operations\n\nManage notebook access, backup, and metadata retrieval.\n\n**Key operations:**\n\n- **List notebooks:** Retrieve all notebooks accessible to a user\n- **Backup notebooks:** Download complete notebook data with optional attachment inclusion\n- **Get notebook IDs:** Retrieve institution-defined notebook identifiers for integration with grants\u002Fproject management systems\n- **Get notebook members:** List all users with access to a specific notebook\n- **Get notebook settings:** Retrieve configuration and permissions for notebooks\n\n**Notebook backup example:**\n\nUse the `scripts\u002Fnotebook_operations.py` script:\n\n```bash\n# Backup with attachments (default, creates 7z archive)\npython3 scripts\u002Fnotebook_operations.py backup --uid USER_ID --nbid NOTEBOOK_ID\n\n# Backup without attachments, JSON format\npython3 scripts\u002Fnotebook_operations.py backup --uid USER_ID --nbid NOTEBOOK_ID --json --no-attachments\n```\n\n**API endpoint format:**\n```\nhttps:\u002F\u002F\u003Capi_url>\u002Fnotebooks\u002Fnotebook_backup?uid=\u003CUID>&nbid=\u003CNOTEBOOK_ID>&json=true&no_attachments=false\n```\n\nFor comprehensive API method documentation, refer to `references\u002Fapi_reference.md`.\n\n### 4. Entry and Attachment Management\n\nCreate, modify, and manage notebook entries and file attachments.\n\n**Entry operations:**\n- Create new entries in notebooks\n- Add comments to existing entries\n- Create entry parts\u002Fcomponents\n- Upload file attachments to entries\n\n**Attachment workflow:**\n\nUse the `scripts\u002Fentry_operations.py` script:\n\n```bash\n# Upload attachment to an entry\npython3 scripts\u002Fentry_operations.py upload --uid USER_ID --nbid NOTEBOOK_ID --entry-id ENTRY_ID --file \u002Fpath\u002Fto\u002Ffile.pdf\n\n# Create a new entry with text content\npython3 scripts\u002Fentry_operations.py create --uid USER_ID --nbid NOTEBOOK_ID --title \"Experiment Results\" --content \"Results from today's experiment...\"\n```\n\n**Supported file types:**\n- Documents (PDF, DOCX, TXT)\n- Images (PNG, JPG, TIFF)\n- Data files (CSV, XLSX, HDF5)\n- Scientific formats (CIF, MOL, PDB)\n- Archives (ZIP, 7Z)\n\n### 5. Site Reports and Analytics\n\nGenerate institutional reports on notebook usage, activity, and compliance (Enterprise feature).\n\n**Available reports:**\n- Detailed Usage Report: User activity metrics and engagement statistics\n- Detailed Notebook Report: Notebook metadata, member lists, and settings\n- PDF\u002FOffline Notebook Generation Report: Export tracking for compliance\n- Notebook Members Report: Access control and collaboration analytics\n- Notebook Settings Report: Configuration and permission auditing\n\n**Report generation:**\n\n```python\n# Generate detailed usage report\nresponse = client.make_call('site_reports', 'detailed_usage_report',\n                           params={'start_date': '2025-01-01', 'end_date': '2025-10-20'})\n```\n\n### 6. Third-Party Integrations\n\nLabArchives integrates with numerous scientific software platforms. This skill provides guidance on leveraging these integrations programmatically.\n\n**Supported integrations:**\n- **Protocols.io:** Export protocols directly to LabArchives notebooks\n- **GraphPad Prism:** Export analyses and figures (Version 8+)\n- **SnapGene:** Direct molecular biology workflow integration\n- **Geneious:** Bioinformatics analysis export\n- **Jupyter:** Embed Jupyter notebooks as entries\n- **REDCap:** Clinical data capture integration\n- **Qeios:** Research publishing platform\n- **SciSpace:** Literature management\n\n**OAuth authentication:**\nLabArchives now uses OAuth for all new integrations. Legacy integrations may use API key authentication.\n\nFor detailed integration setup instructions and use cases, refer to `references\u002Fintegrations.md`.\n\n## Common Workflows\n\n### Complete notebook backup workflow\n\n1. Authenticate and obtain user ID\n2. List all accessible notebooks\n3. Iterate through notebooks and backup each one\n4. Store backups with timestamp metadata\n\n```bash\n# Complete backup script\npython3 scripts\u002Fnotebook_operations.py backup-all --email user@example.edu --password AUTH_TOKEN\n```\n\n### Automated data upload workflow\n\n1. Authenticate with LabArchives API\n2. Identify target notebook and entry\n3. Upload experimental data files\n4. Add metadata comments to entries\n5. Generate activity report\n\n### Integration workflow example (Jupyter → LabArchives)\n\n1. Export Jupyter notebook to HTML or PDF\n2. Use entry_operations.py to upload to LabArchives\n3. Add comment with execution timestamp and environment info\n4. Tag entry for easy retrieval\n\n## Python Package Installation\n\nInstall the `labarchives-py` wrapper for simplified API access:\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fmcmero\u002Flabarchives-py\ncd labarchives-py\nuv pip install .\n```\n\nAlternatively, use direct HTTP requests via Python's `requests` library for custom implementations.\n\n## Best Practices\n\n1. **Rate limiting:** Implement appropriate delays between API calls to avoid throttling\n2. **Error handling:** Always wrap API calls in try-except blocks with appropriate logging\n3. **Authentication security:** Store credentials in environment variables or secure config files (never in code)\n4. **Backup verification:** After notebook backup, verify file integrity and completeness\n5. **Incremental operations:** For large notebooks, use pagination and batch processing\n6. **Regional endpoints:** Use the correct regional API endpoint for optimal performance\n\n## Troubleshooting\n\n**Common issues:**\n\n- **401 Unauthorized:** Verify access key ID and password are correct; check API access is enabled for your account\n- **404 Not Found:** Confirm notebook ID (nbid) exists and user has access permissions\n- **403 Forbidden:** Check user permissions for the requested operation\n- **Empty response:** Ensure required parameters (uid, nbid) are provided correctly\n- **Attachment upload failures:** Verify file size limits and format compatibility\n\nFor additional support, contact LabArchives at support@labarchives.com.\n\n## Resources\n\nThis skill includes bundled resources to support LabArchives API integration:\n\n### scripts\u002F\n\n- `setup_config.py`: Interactive configuration file generator for API credentials\n- `notebook_operations.py`: Utilities for listing, backing up, and managing notebooks\n- `entry_operations.py`: Tools for creating entries and uploading attachments\n\n### references\u002F\n\n- `api_reference.md`: Comprehensive API endpoint documentation with parameters and examples\n- `authentication_guide.md`: Detailed authentication setup and configuration instructions\n- `integrations.md`: Third-party integration setup guides and use cases\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Flabarchive-integration",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add davila7\u002Fclaude-code-templates --skill labarchive-integration",{"tool":64,"command":65},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill labarchive-integration",{"tool":67,"command":68},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill labarchive-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Flabarchive-integration\u002FSKILL.md",true,[72,78,82,86,92,96],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fapi_reference.md","REFERENCE","参考文档",9012,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Flabarchive-integration\u002Freferences\u002Fapi_reference.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fauthentication_guide.md",10709,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Flabarchive-integration\u002Freferences\u002Fauthentication_guide.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fintegrations.md",12645,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Flabarchive-integration\u002Freferences\u002Fintegrations.md",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fentry_operations.py","SCRIPT","脚本",10576,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Flabarchive-integration\u002Fscripts\u002Fentry_operations.py",{"path":93,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fnotebook_operations.py",8677,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Flabarchive-integration\u002Fscripts\u002Fnotebook_operations.py",{"path":97,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fsetup_config.py",6412,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Flabarchive-integration\u002Fscripts\u002Fsetup_config.py",[101,127,154,186,221,245],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":43},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[107],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[109,110,111,112,113,27,114,115,116,117,118,30,119,120,121,122,123,124,125,126],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","when","reduce","record","track","verdict","evm","solana","how","public","look",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":43},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[133],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[135,136,137,138,139,140,141,142,143,144,145,117,146,147,148,149,150,151,152,153],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":169,"publishedAt":43},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[160,163,164],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":165,"categoryName":166,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[170,171,172,173,174,175,176,27,177,178,179,180,181,182,183,116,38,184,117,185],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","database","query",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":190,"licenseFileUrl":191,"sourceHtmlUrl":192,"categories":193,"keywords":197,"publishedAt":43},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[194],{"categoryNo":195,"categoryName":196,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,27,220],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":190,"licenseFileUrl":225,"sourceHtmlUrl":226,"categories":227,"keywords":232,"publishedAt":43},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[228,231],{"categoryNo":229,"categoryName":230,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":195,"categoryName":196,"taxonomyType":21,"taxonomyTypeDesc":22},[233,234,235,236,237,199,238,208,209,239,240,241,242,27,243,30,244],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":246,"name":247,"nameZh":6,"description":248,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":190,"licenseFileUrl":249,"sourceHtmlUrl":250,"categories":251,"keywords":259,"publishedAt":43},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[252,255,256],{"categoryNo":253,"categoryName":254,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":257,"categoryName":258,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000036","内容创作者",[260,261,262,263,264,265,266,267,201,268,211,146,269,270,271,272,273,182,274,117,275,276,277,278,279,124,280],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]