Collect diagnostic evidence for Apollo.io API problems, including environment details, connectivity, API key type, rate limits, and endpoint checks. Save the findings as a JSON file that can accompany a support ticket.
Build an application layer that controls team access to Apollo.io APIs. It helps define role permissions, issue scoped and expiring API keys, route requests through an Express proxy, and provide administrative key and usage endpoints.
Test an Apollo.io integration with small examples for people search and person or company enrichment, which adds further details. TypeScript and Python examples help check API credentials and understand the returned data.
Respond to Apollo.io API incidents with severity classification, diagnostic scripts, and recovery procedures. Use temporary call blocking and cached responses to handle failures, then document the timeline, customer impact, and corrective actions in a post-incident review.
Set up Apollo.io API access in TypeScript or Python by configuring an HTTP client, API key headers, and environment variables. Verify authentication with a health check and troubleshoot missing keys, insufficient permissions, rate limits, and network errors.
Set up a local development workflow for Apollo.io integrations with environment templates, sandbox keys, request logging, and test commands. Use MSW to simulate API responses offline and Vitest to check changes against synthetic data.
Analyze Claude API spending and test cost controls through model selection, caching repeated input, batch processing, and output limits. Track budgets and compare cost, quality, and response time before expanding a proposed change.
Collect a reviewed diagnostic bundle for persistent Claude API problems or a support ticket. It records request IDs, rate-limit headers, SDK and runtime versions, and connectivity details while excluding API keys and customer prompt or response content.
Prepare Claude API services for deployment using Docker, Cloud Run, or Kubernetes. Configure runtime secrets, health checks, staging tests, gradual releases, and rollback procedures, then document deployment evidence without exposing credentials or request content.
Set up organization, Workspace, and role-based access rules for Anthropic teams. The skill helps map people and services to limited permissions, constrain model and usage access, and plan key rotation, revocation, and sandbox checks.
Review an Algolia integration for exposed write-capable keys, overly broad index access, and records visible to search users. The skill maps credentials and permissions, checks tenant restrictions, and produces findings, remediation steps, and a key rotation plan.
Assess whether an Anima and Figma design-to-code pipeline is ready for production. Review credentials, source traceability, generated-code and visual checks, monitoring, and rollback evidence, then produce a go/no-go record for release owners.
Implement and validate Algolia search interaction events such as clicks, conversions, and views, while keeping them distinct from database-to-index updates. Use it to define event identity and consent handling, then check retries, duplicates, and reconciliation behavior.
Assess current infrastructure use across CPU, memory, storage, network, and request rates, then use historical trends to estimate future needs. The skill identifies possible bottlenecks and outlines vertical or horizontal scaling options with cost estimates for capacity planning.
Create a focused JSON diagnostic bundle for Anima SDK or Figma integration failures. It records SDK and Node.js versions, token presence without token values, and connectivity status, so you can review and redact evidence before attaching it to a support request.
Audit project libraries for known security vulnerabilities, outdated versions, and license issues across several package ecosystems. Trace problems through indirect dependencies and produce prioritized findings, upgrade commands, and alternatives for packages that are no longer maintained.
Analyze application logs to find slow requests, recurring errors, and unusual resource usage. Group related issues into reports with response times, error frequencies, and recommendations for performance improvements and clearer logging.
Track Anima generation usage, reuse outputs when their source and settings still match, and regenerate only changed design elements. It helps teams review plan fit using current account data and report avoided work without guessing monetary savings.
Assess crypto market mood with the Fear & Greed Index, news keywords, and price and volume momentum. Get a 0–100 composite score and component breakdown for the overall market or a selected coin, with options to view trends or export JSON.
Examine an application's network requests and their latency to locate communication bottlenecks. Get practical recommendations such as parallel requests, batching, connection reuse, or timeout adjustments to improve API and page load performance.
Set up privacy practices for Claude API workflows, including redacting personal data before requests, scanning responses, and logging request metadata without message content. Produce a sanitized handling record with retention and deletion outcomes.
Upgrade Anima SDK integrations or move manual Figma exports into automated code generation. Compare generated files against a baseline, validate changes in staging, and document the package version, test results, and rollback reference.
Build a review-driven pipeline that scans approved Figma components, generates React code with the Anima SDK, and detects design changes. It confines generated files to approved paths and prepares a change for review before code is accepted.
Analyze liquidity pools on Uniswap, Curve, and Balancer using deposits, trading volume, and fees. Estimate returns from supplying funds, compare price-change losses against holding tokens, and export pool comparisons as JSON or CSV.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)