performing-regression-analysis
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill performing-regression-analysisExecute 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'.
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill content is largely boilerplate with minimal actionable guidance. It explains what regression analysis is (which Claude already knows) rather than how to use the specific regression-analysis-tool plugin. The absence of any concrete code, API calls, or tool-specific commands makes this skill essentially unusable for its stated purpose.
Suggestions
Add concrete, executable examples showing how to invoke the regression-analysis-tool plugin with specific parameters and expected output formats
Remove generic sections (Prerequisites, Error Handling, Resources) that contain no skill-specific information and the redundant overview
Include actual API/command syntax for the regression-analysis-tool plugin, such as function calls, required parameters, and return value schemas
Add a validation workflow showing how to verify model quality and what thresholds indicate acceptable performance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with redundant explanations (overview repeated twice), explains obvious concepts Claude already knows (what regression is, what R-squared means), and includes generic boilerplate sections (Prerequisites, Instructions, Error Handling) that add no skill-specific value. | 1 / 3 |
Actionability | No executable code, no specific commands, no concrete API calls to the regression-analysis-tool plugin. Examples describe what 'the skill will do' abstractly rather than showing how to actually invoke the tool or what parameters to pass. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists abstract phases without any concrete steps, validation checkpoints, or error recovery. The 'Instructions' section is completely generic ('invoke this skill when trigger conditions are met') with no actual workflow guidance. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but it's a monolithic document with no references to external files for detailed API documentation or advanced usage. The structure exists but contains mostly filler content rather than appropriately split detailed materials. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
27%This description suffers from a mismatch between its specific capability (regression analysis) and its overly generic trigger terms. The truncated text ('performa...') suggests incomplete content, and phrases like 'empowers AI assistant' add no value. The generic triggers would cause this skill to compete with many other analytical skills unnecessarily.
Suggestions
Replace generic triggers with regression-specific terms: 'Use when the user mentions regression, linear model, polynomial fit, predicting values, correlation analysis, or fitting data to a model'
Remove fluff like 'empowers AI assistant' and fix the truncated description to list complete, specific capabilities
Make the 'Use when' clause specific to regression scenarios rather than generic 'analyzing code or data'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (regression analysis) and some actions (analyzes datasets, generates models, validates), but the description is truncated and uses vague language like 'empowers AI assistant' which is fluff. | 2 / 3 |
Completeness | Has a 'what' (regression analysis) and includes a 'Use when...' clause, but the 'when' is too generic ('analyzing code or data') and doesn't specifically guide when to choose this skill over others. | 2 / 3 |
Trigger Term Quality | The trigger terms 'analyze', 'review', 'examine' are overly generic and would match almost any analytical task. Missing specific terms users would say like 'regression', 'linear model', 'predict', 'correlation', 'fit data'. | 1 / 3 |
Distinctiveness Conflict Risk | The triggers 'analyze', 'review', 'examine' combined with 'code or data' would conflict with virtually any data analysis, code review, or examination skill. Not distinctive to regression analysis. | 1 / 3 |
Total | 6 / 12 Passed |
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.