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'.

Quality

13%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

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.md

Quality

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.

This description suffers from a mismatch between its somewhat specific capability (regression analysis) and its extremely generic trigger guidance. The trigger terms ('analyze', 'review', 'examine') and use-when clause ('analyzing code or data') would cause this skill to fire for nearly any analytical task, creating high conflict risk. Additionally, the description is truncated, uses first/second-person-adjacent phrasing ('empowers AI assistant'), and includes filler language.

Suggestions

Replace the generic trigger terms with regression-specific terms like 'regression', 'linear model', 'polynomial fit', 'predict', 'correlation', 'R-squared', 'curve fitting'.

Rewrite the 'Use when' clause to be specific: 'Use when the user asks for regression analysis, fitting models to data, predicting outcomes from variables, or building linear/polynomial models.'

Fix the truncated description and remove filler language like 'empowers AI assistant'; 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 overly generic ('analyzing code or data') and the trigger phrases are too broad to be useful. 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', or 'correlation' are missing from the trigger guidance.	1 / 3
Distinctiveness Conflict Risk	The trigger terms 'analyze', 'review', and 'examine' would conflict with virtually any data analysis, code review, or examination skill. The 'Use when analyzing code or data' clause is far too broad to distinguish this from other analytical skills.	1 / 3
	Total	6 / 12 Passed

Implementation

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

This skill content is almost entirely generic boilerplate with no actionable, concrete guidance. It never shows how to actually invoke the regression-analysis-tool plugin, provides no executable code or commands, and pads extensively with concepts Claude already understands. The content reads like a marketing description rather than an operational skill file.

Suggestions

Replace the abstract workflow description with concrete, executable steps showing actual plugin invocation syntax (e.g., specific function calls, parameters, and expected output formats for the regression-analysis-tool).

Remove all generic boilerplate sections (Prerequisites, Error Handling, Output, Integration) that contain no skill-specific information, and cut the 'When to Use' section which restates obvious trigger conditions.

Add at least one complete, copy-paste-ready example showing input data format, the exact plugin call, and expected output with specific metrics.

Include explicit validation checkpoints in the workflow (e.g., 'Check residual plots for heteroscedasticity before accepting model') with concrete commands or code to perform each check.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive padding. Explains concepts Claude already knows (what regression is, what R-squared means), includes generic boilerplate sections ('Error Handling', 'Prerequisites', 'Instructions') that add no actionable value, and the 'When to Use This Skill' section restates the obvious. Nearly every section could be cut or drastically shortened.	1 / 3
Actionability	No concrete code, commands, or executable guidance anywhere. The examples describe what the skill 'will do' in abstract terms rather than showing 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 ('Data Analysis → Model Generation → Model Validation → Performance Reporting') are vague descriptions without any concrete commands, validation checkpoints, or error recovery loops. There's no indication of what tools to call, what parameters to pass, or how to verify results at each step.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files or resources. The 'Resources' section lists 'Project documentation' and 'Related skills and commands' without any actual links. Content is poorly organized with redundant sections (Overview, How It Works, When to Use, Instructions all overlap significantly).	1 / 3
	Total	4 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 4dee593

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.