Agent Skills: ecosystem-integrity-scanner
>-
ID: oimiragieo/agent-studio/ecosystem-integrity-scanner
416
Install this agent skill to your local
Skill Files
The files that make up ecosystem-integrity-scanner.
More agent skills
- orlixPersonal AI Operating System on Base. Use when an agent wants to analyze any Base token (live price, risk verdict, liquidity), chat with 19 frontier AI models (Claude, GPT-4o, Grok, Gemini, DeepSeek), deploy or manage B20 tokens (Base Beryl native precompile — config validation, ABI-encoded deployment tx, live gas + nonce from Base RPC), check ETH or ERC-20 balances, get current gas prices, read any ERC-20 on Base, or verify a tx receipt. No auth required.
- ops-inspectorAIOps-style CloudBase inspection skill (v3). Use when users need health checks, log diagnosis, alarm interpretation (CPU alert normal?, peak QPS), metrics via queryEnv(action=metrics), or fault playbooks for 429 / function 404 / ACCESS_TOKEN_INVALID / zero invocations. Triggers on 巡检, 诊断, 告警, 峰值 QPS, 限频, 调用量为 0, troubleshooting.
- release-itBuild production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or "make it resilient". Also trigger when designing resilient microservices, planning zero-downtime deployments, or capacity-planning for peak load. Covers stability patterns, capacity planning, deploy/release decoupling, and observability. For data systems, see ddia-systems. For system architecture, see system-design.
- simplifyRefactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
- bump-versionUse when bumping the AionUi version: query AionCore release, verify artifacts, update package.json, generate CHANGELOG, branch, commit, push, create PR, auto-merge, tag release.
- incident-runbook-templatesCreate structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use this skill when building a service outage runbook for a payment processing system; creating database incident procedures covering connection pool exhaustion, replication lag, and disk space alerts; onboarding new on-call engineers who need step-by-step recovery guides written for a 3 AM brain; or standardizing escalation matrices across multiple engineering teams.