performing-regression-analysis
Execute this skill empowers AI assistant to perform regression analysis and modeling using the regression-analysis-tool plugin. it analyzes datasets, generates appropriate regression models (linear, polynomial, etc.), validates the models, and provides performa... Use when analyzing code or data. Trigger with phrases like 'analyze', 'review', or 'examine'.
23
13%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/ai-ml/regression-analysis-tool/skills/performing-regression-analysis/SKILL.mdQuality
Discovery
27%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies regression analysis as its domain but is severely undermined by overly generic trigger terms ('analyze', 'review', 'examine') that would cause frequent false matches. The description is truncated, uses first/second-person-adjacent phrasing ('empowers AI assistant'), and the 'Use when' clause is too broad to be useful for skill selection among multiple skills.
Suggestions
Replace generic trigger terms with regression-specific keywords like 'regression', 'linear model', 'polynomial fit', 'predict outcomes', 'correlation', 'R-squared', 'curve fitting'.
Narrow the 'Use when' clause from 'analyzing code or data' to something like 'Use when the user needs to fit regression models to data, predict numerical outcomes, or evaluate model performance metrics'.
Fix the truncated description, remove the 'empowers AI assistant' phrasing, and use third person voice (e.g., 'Performs regression analysis on datasets...').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (regression analysis) and some actions (analyzes datasets, generates regression models, validates models), but the description is truncated ('performa...') and mixes in vague filler language like 'empowers AI assistant'. | 2 / 3 |
Completeness | It partially answers 'what' (regression analysis and modeling) and has a 'Use when' clause, but the 'when' is far too generic ('analyzing code or data') and doesn't meaningfully guide skill selection. The description is also truncated, losing information. | 2 / 3 |
Trigger Term Quality | The trigger terms 'analyze', 'review', and 'examine' are extremely generic and not specific to regression analysis. Natural terms like 'regression', 'linear model', 'polynomial fit', 'predict', 'correlation', or 'R-squared' are missing from the trigger guidance. | 1 / 3 |
Distinctiveness Conflict Risk | The trigger terms 'analyze', 'review', 'examine' and the scope 'code or data' are so broad that this would conflict with virtually any data analysis, code review, or general analysis skill. | 1 / 3 |
Total | 6 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is almost entirely generic boilerplate with no actionable content. It never shows how to actually use the regression-analysis-tool plugin—no API calls, no code examples, no parameter specifications, no concrete commands. The majority of the content describes abstract concepts Claude already understands or contains placeholder text that provides zero guidance.
Suggestions
Replace the abstract 'How It Works' and 'Examples' sections with concrete, executable code showing how to invoke the regression-analysis-tool plugin with specific parameters and data formats.
Add a concrete workflow with actual commands/API calls, including validation steps (e.g., checking R-squared thresholds, residual plots) and error recovery for common failure modes.
Remove all generic filler sections ('Prerequisites', 'Instructions', 'Output', 'Error Handling', 'Resources') that contain only placeholder text, and replace with specific plugin configuration, input/output schemas, and actual error codes.
Document the regression-analysis-tool plugin's interface: what functions/endpoints it exposes, what data formats it accepts, and what outputs it returns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanation of concepts Claude already knows. Sections like 'When to Use This Skill', 'How It Works', 'Integration', 'Prerequisites', 'Instructions', 'Output', 'Error Handling', and 'Resources' are all filler with no actionable content. The entire file could be reduced to a fraction of its size. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance anywhere. The examples describe what the skill 'will do' in vague terms without showing any actual code, API calls, or plugin invocations. The 'Instructions' section is entirely generic ('Invoke this skill when the trigger conditions are met') with no specifics about how to use the regression-analysis-tool plugin. | 1 / 3 |
Workflow Clarity | The workflow steps are abstract descriptions ('analyze the provided data', 'generate a regression model') with no concrete commands, validation checkpoints, or error recovery loops. There is no indication of how to actually invoke the regression-analysis-tool plugin, what parameters it accepts, or how to validate outputs. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files and no bundle files provided. Multiple sections contain placeholder-quality content ('The skill produces structured output relevant to the task') that adds no value. No meaningful structure or navigation exists. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
69c73e9
- 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.