Big model smell

Skill nahiddotai/operator-powers/plugins/operator-powers/skills/big-model-smell

AI skills to operate and grow. Twenty-eight practical powers for non-technical operators.

Install

npx -y skills add nahiddotai/operator-powers --skill big-model-smell

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Simplify an oversized prompt, plan, workflow, document, system, or build when its complexity, context, automation, or model cost is not earning its keep.

SKILL.md

2.1 KB, as published. Nobody here has run it

Big Model Smell

Find where complexity, context, automation, or model capability exceeds the actual job, then simplify without losing the required outcome.

Job contract

Owns: simplification of one supplied artifact, workflow, prompt, system, or plan.
Does not own: retrospective analysis across recent sessions (operator-audit).
Finished deliverable: complexity diagnosis, smallest viable design, migration steps, and verification criteria.

Smells to inspect

One giant prompt trying to perform unrelated jobs.
A frontier model used for deterministic extraction or formatting.
Too many agents, tools, files, approval steps, or moving parts.
Context loaded “just in case” rather than for a decision.
An automation that costs more to maintain than the task costs to do.
A document or system no operator can confidently change.

Workflow

State the outcome and non-negotiable constraints.
Map every component to the outcome it supports.
Mark components as essential, useful, unproven, duplicate, or decorative.
Identify the cheapest adequate level for each step: rule, template, small model, large model, human judgment, or automation.
Design the smallest version that preserves safety and quality.
Give a reversible migration order and a test that proves nothing important was lost.

Output

# Complexity Review

## Required Outcome
[What must remain true]

## Big-Model Smells
[Evidence and cost of each]

## Keep, Simplify, Remove, Test
[Decision table]

## Smaller Working Design
[New flow]

## Safe Migration
[Reversible sequence]

## Verification
[Tests and stop conditions]

Guardrails

Do not simplify away approval, privacy, security, accessibility, or recovery controls.
Do not assume a cheaper model is adequate; define a representative test.
Never modify or delete the original artifact without explicit approval.