regression

regression is a skill for Claude Code from ChrisGVE/localdata-mcp. It costs 24 tokens per session (644 once invoked), scanned A, original, Apache-2.0.

A workflow for building models that predict a target value from other data columns. It checks the data, creates a linear baseline, and evaluates measures such as prediction error and how much variation the model explains.

In plain words
What is it for?
Use it to explore a database, select numeric predictors, build regression models, and compare their results.
Why use it?
It provides a repeatable process for checking whether features can predict an outcome and whether the model is useful.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the localdata-mcp plugin — 18 skills, 11 agents, 1 MCP server shipped together

Good fit Use it to explore a database, select numeric predictors, build regression models, and compare their results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chrisgve/localdata-mcp/regression
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ChrisGVE/localdata-mcp --skill regression
Clone the repo
git clone --depth 1 https://github.com/ChrisGVE/localdata-mcp

Made for: Claude Code.

Or install localdata-mcp, the plugin that ships this one along with the rest of its 18 skills, 11 agents, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for regression

README.md
[![agentmods](https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/regression/github.svg)](https://agentmods.dev/skills/chrisgve/localdata-mcp/regression)
Your own site
<a href="https://agentmods.dev/skills/chrisgve/localdata-mcp/regression"><img src="https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/regression/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for regression

Your own site · 80×15
<a href="https://agentmods.dev/skills/chrisgve/localdata-mcp/regression"><img src="https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/regression.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 644 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00644
Opus 5 $0.00012 $0.00322
Sonnet 5 $0.00005 $0.00129
Haiku 4.5 $0.00002 $0.00064

Measured 10d ago against content hash 67938c8a7af1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

regression scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/modeling/regression/SKILL.md · 45 lines

How it starts

The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Regression

Build, evaluate, and compare regression models to predict a target variable from features.

Steps

  1. Parse arguments. Extract the database name and target column from $ARGUMENTS. The first argument is the database name, the second is the target variable to predict.

  2. Explore available features. Call describe_database with the database name. Identify numeric columns as potential predictors. Note the target column's distribution (continuous vs discrete) to confirm regression is appropriate.

  3. Extract and inspect data. Call execute_query to select the target column and candidate feature columns. Check for nulls, outliers, and sufficient row count (at least 30 observations per feature as a rule of thumb).

  4. Build a linear baseline. Call analyze_regression with the database name, target column, feature columns, and model type "linear". Review the results: R-squared, adjusted R-squared, coefficients, p-values, and residual diagnostics.

  5. Evaluate baseline performance. Call evaluate_model_performance to get detailed metrics: RMSE, MAE, R-squared, and residual analysis. Assess whether the linear model captures the relationship adequately.

  6. Interpret baseline results. Check for:

    • R-squared below 0.3: poor fit, consider non-linear models
    • Features with p-values above 0.05: candidates for removal
    • Multicollinearity: correlated predictors inflating variance
    • Residual patterns: non-random residuals suggest model misspecification
  7. Try alternative models if needed. If the linear baseline performs poorly (R-squared below 0.5 or patterned residuals), call analyze_regression with alternative model types:

    • "ridge" for multicollinearity issues
    • "lasso" for feature selection (many predictors)
    • "polynomial" for curved relationships
  8. Compare models. For each model fitted, compare R-squared, RMSE, and MAE. Select the model with the best balance of performance and interpretability. Simpler models are preferred when performance is comparable.

Read the full file on GitHub · 45 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 45 lines · 24 tokens per session scan A 67938c8a7af1

Subscribe to this mod's changes

regression is a skill published in the GitHub repository ChrisGVE/localdata-mcp (4 stars, last pushed 26d ago), licensed Apache-2.0. It adds 24 tokens to every session and 644 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

wingman-mcp

Add persistent, interactive task plan management to your agent. Wingman tracks plans and tasks across a long conversation — Claude creates plans, ticks tasks after completing work, and a live panel renders inline in the chat. Install the MCP server first, then use these tools to manage plans and tasks throughout any…

adeoluwaadesina/wingman-mcp · 68 tokens

liveagent-code-review

Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.

Stack-Cairn/LiveAgent · 54 tokens

skills-creator

Create or update LiveAgent runtime skills. Use when you need to summarize a workflow into a skill, write it into the fixed user skills root, validate it, package it, or refine a skill's references for LiveAgent's SkillsManager flow.

Stack-Cairn/LiveAgent · 53 tokens

skills-installer

Install, list enabled, validate, or package LiveAgent skills. Use when you need to inspect the skills enabled in the current conversation, import a local skill directory or package, search/install from ClawHub, install from a GitHub repo/tree URL, or reconcile conflicts during an upgrade.

Stack-Cairn/LiveAgent · 62 tokens

triaging-incidents

Creating, triaging, updating, and analyzing ServiceNow incidents. Assess severity, check affected CIs, find related incidents, and recommend assignments. Use when the user mentions incidents, INC numbers, outages, service disruptions, ticket creation, triage, priority, severity, ITSM operations, SLA breaches…

jschuller/mcp-server-servicenow · 82 tokens

reviewing-update-sets

Reviewing, analyzing, and comparing ServiceNow update sets before promotion. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, "what changed in this update set," or…

jschuller/mcp-server-servicenow · 77 tokens