aeon-skill-repair
Auto-diagnose and fix a failing or degraded installed skill. Reads the SKILL.md plus recent error output, classifies the failure (api-change / rate-limit / timeout / sandbox-limitation / prompt-bug / output-format / missing-secret / config), applies the smallest fix that addresses the root cause, and attaches a verification recipe. Minimum-edit principle, never auto-applies high-risk changes. Triggers: "fix this skill", "skill X is broken", "diagnose this failure", "the output of X looks wrong".
What this skill does
# aeon-skill-repair Targeted repair for one failing skill. Build a diagnostic dossier, classify the failure, apply the matching playbook, attach a verification recipe. ## Inputs | Param | Description | |---|---| | `target` | Skill name or SKILL.md path. Required. | | `error_output` | Recent failed output (paste from run log). Required if not auto-detectable. | | `mode` | `repair` (default) or `dry-run` (diagnose only). | ## Diagnosis sources - The skill file (frontmatter, declared sources, env-var references). - Error output signature (HTTP codes, common API errors, rate-limit hits, refusal markers). - Source liveness — WebFetch on referenced URLs to detect 404s, redirects, schema changes. - Frontmatter integrity (valid YAML). ## Failure categories and fix scope | Category | Detection | Fix scope | |---|---|---| | `api-change` | 404/410, schema mismatch | Update endpoints/payload/headers per live spec. Cite the spec URL. | | `rate-limit` | 429, "too many requests" | Add backoff or fallback endpoint. Never raise the limit. | | `timeout` | Killed mid-run, partial output | Stage the work, add early-return on partial success. | | `sandbox-limitation` | Auth-bearing curl fails | Convert to prefetch / postprocess pattern. | | `prompt-bug` | Hallucination, refusal, missing required section | Minimum-edit specificity insertion. < 30 lines diff. | | `output-format` | Output passes execution but fails downstream parser | Edit until next run satisfies the failing assertion. | | `missing-secret` | "API key missing", env var unset | **No code change.** Name the missing var for the operator. Exit `REPAIR_DIAGNOSED_NO_FIX`. | | `config` | Bad input config (watchlist, list file) | Fix obvious shape errors. Never invent entries. | | `unknown` | None of the above | Don't edit blindly. Append dossier to repair-notes, exit `REPAIR_DIAGNOSED_NO_FIX`. | ## Risk classes - **LOW** — fallback added, comment-only, < 30 lines. Auto-applied. - **MED** — data source change, output format edit. Auto-applied with verification recipe. - **HIGH** — touches behavior fundamentally, changes defaults. **Operator review required, not auto-applied.** ## Verification recipe (every repair) ``` 1. Re-run the skill: <one-line invocation> 2. Expected: <category-specific signal — "no rate-limit in trace" / "≥ 200 words" / "matches pattern X"> 3. If still failing: <fallback path> ``` ## Cooldown 24h cooldown per skill — prevents repair loops on fixes that didn't stick. State in local `repair-history.json`. ## Rules - One target per run. Never bundle unrelated repairs. - Minimum-edit principle. Small diffs. - Never modify env-var configuration. Missing secrets are flagged for the operator. - Inside a git repo: branch + diff, never directly to main.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.