CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

forecasting

Build and validate neuro-divergent univariate RNN or baseline forecasts with keyed dates, chronological splits, past-only scaling, explicit conformal residual intervals, and bounded checkpoints. Use for forecasting APIs, training correctness, evaluation leakage, calendar behavior, or persistence.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality skill body: specific, executable, and sequenced with real verification and diagnosis loops, plus a well-signaled one-level-deep reference bundle. Weakest spot is conciseness — the conformal section in particular mixes API contract with general conformal-prediction caveats that could be tightened or moved to the reference.

Suggestions

Trim or relocate the general conformal-theory caveats (exchangeability, distribution shift) to references/evaluation.md, keeping only the API-specific consequences in the body.

Inline a short executable RNN/ModelAdapter example alongside the baseline example so the learned-model path is as copy-paste ready as the naive path.

The two identical links to references/evaluation.md could be consolidated into one clearly-labeled pointer to save tokens.

DimensionReasoningScore

Conciseness

The body is dense and almost entirely API-specific contract detail (exact formulas like "ceil((n + 1) * coverage)", method behaviors, error conditions) rather than filler, assuming Claude's competence throughout. A few stretches read as general ML wisdom Claude already knows (e.g., "distribution shift and model retraining can invalidate calibration", "Classical marginal coverage relies on appropriate exchangeability") and the conformal section's constraint enumerations could be trimmed, keeping this at the 4 anchor rather than 5.

4 / 5

Actionability

Concrete, near-copy-paste guidance dominates: a complete runnable Rust baseline example, the exact conformal API sequence, and three exact cargo test commands with env vars. The main gap keeping it below 5 is that the core learned-model flow (RNN via "ModelAdapter::new(name, model, lookback, frequency)") is described in prose and delegated to a repo example file rather than shown as executable code, fitting the 4 anchor (mostly executable, minor gaps).

4 / 5

Workflow Clarity

Sections form a coherent sequence (data contract → baseline → implement/evaluate → calibrate → persist → verify → accept/diagnose) with explicit validation: the numbered data-contract checks ("Validate finite targets, unique timestamps and regular frequency"), the exact Verify commands, and an Acceptance section with a diagnosis feedback loop ("For an unexpectedly strong score, inspect leakage, overlap with pretrained data, key alignment and the naive baseline"). This matches the 5 anchor's explicit checkpoints plus error-recovery loops.

5 / 5

Progressive Disclosure

The bundle structure is clean: SKILL.md (~120 lines, well-sectioned) holds the working contract, and the single deeper detail file references/evaluation.md exists, is linked twice at points of need ([evaluation and migration details](references/evaluation.md)), and is one level deep with no further nesting. The split is appropriate — limits, regression cases, and research boundaries live in the reference while the body keeps instructions — matching the 5 anchor.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete, comprehensive, and anchored to a specific library, with an explicit "Use for..." trigger clause covering the skill's main use cases. The only improvement space is adding a few more natural trigger synonyms such as "time series" or "save/load".

Suggestions

Consider adding common user phrasings like "time series", "cross-validation", or "save/load checkpoints" to the trigger clause to broaden natural-term coverage.

"Persistence" is slightly formal; "saving or loading models" would match how users more often phrase it.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — "Build and validate neuro-divergent univariate RNN or baseline forecasts with keyed dates, chronological splits, past-only scaling, explicit conformal residual intervals, and bounded checkpoints" — each mapping to a real section of the skill (training, evaluation, leakage, intervals, persistence). Coverage is comprehensive for the skill's scope with no vague filler, matching the 5 anchor rather than 4, which would require minor gaps.

5 / 5

Completeness

Both halves are explicit: a clear "what" ("Build and validate... forecasts with keyed dates, chronological splits, past-only scaling, explicit conformal residual intervals, and bounded checkpoints") and an explicit "when" with concrete trigger phrases ("Use for forecasting APIs, training correctness, evaluation leakage, calendar behavior, or persistence"). This mirrors the 5 anchor's structure exactly; a 4 would require the when-clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Triggers include natural phrases users would say: "forecasting APIs, training correctness, evaluation leakage, calendar behavior, or persistence" plus "conformal residual intervals" and "checkpoints". A few common synonyms are missing (e.g., "time series", "save/load", "cross-validation", "backtesting"), which fits the 4 anchor (good coverage, a few natural terms missing) rather than the 5 anchor's synonym-level coverage.

4 / 5

Distinctiveness Conflict Risk

The description is anchored to a specific library and workflow ("neuro-divergent univariate RNN or baseline forecasts", "conformal residual intervals", "bounded checkpoints"), giving it a clear niche with minimal overlap risk against generic forecasting, data-analysis, or ML skills. It would not plausibly trigger the wrong skill.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ruvnet/ruv-FANN

Path

plugins/ruv-fann/skills/forecasting/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.