mechanism-derivation

Derive model architectures, objectives, and learning rules from first principles.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/tiendungchs/PersonalWiki --skill mechanism-derivation-tiendungchs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mechanism-derivation
Source: https://github.com/tiendungchs/PersonalWiki/tree/main/.claude/skills/mechanism-derivation
Command: npx skills add https://github.com/tiendungchs/PersonalWiki --skill mechanism-derivation-tiendungchs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When designing or explaining a machine learning model, equations and architectures often feel arbitrary — softmax here, sigmoid there, a loss term bolted on. This Skill provides a disciplined method for deriving each component so it is forced by a constraint rather than asserted, and for stress-testing the result afterward. ## Core Features & Use Cases - Derivation moves: Read free variables out of an equation, cancel intractable terms via ratios or symmetries, derive functional forms (exponential, sigmoid, softmax) from constraints, and name the leftover gaps that become the next hard problem. - Architecture construction: Build global objectives from local per-part quantities, solve the single-item case exactly, frame new models as N named modifications to understood ones, and justify every restriction by what it buys computationally. - Interrogation and validation: Trace one concrete input end-to-end, choose the scaling axis where the mechanism must diverge from a baseline, probe internal units, run capacity and interference analysis, perturb input statistics, and extract falsifiable predictions. - Use Case: You are reading a paper on Hopfield networks or designing a new objective and the equations feel arbitrary. Apply this Skill to derive the energy function from local connection happiness, derive the Hebbian rule from the N=1 case, and identify the capacity limit and failure mode before writing any code. ## Quick Start Use the mechanism-derivation skill to derive the loss function and update rule for my model so each piece is forced rather than asserted, then stress-test the design.

Frequently Asked Questions about mechanism-derivation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I derive a loss function instead of choosing one by convention?▼

Turn the desired capability into a concrete trainable task, such as next-observation prediction, then argue that the property you want is the cheapest way to minimize that loss. Derive functional forms like softmax or sigmoid from constraints rather than asserting them.

How to understand a paper whose equations feel arbitrary?▼

Read each equation for its free variables to find the system's components, then ask what constraint forces each functional form. Frame the model as N named modifications to one you already understand and follow each modification's consequences.

How do I test whether a model learned structure or a shortcut?▼

Probe internal units rather than relying on aggregate metrics, and choose a scaling axis where the claimed mechanism predicts a different curve than a dumb baseline, such as nodes visited versus edges visited. Perturbing the input data distribution is another sharp probe.

When should I approximate an intractable term like a partition function?▼

Only after searching for a ratio, difference, or symmetry that cancels it exactly, since exact cancellation beats good approximation and is often available. If the term survives, name the leftover explicitly because that gap is usually the field's next hard problem.

What is the difference between mechanism-derivation and derive-dont-declare?▼

The derive-dont-declare skill covers problem-framing moves like killing the naive solution with a number and dissolving ill-posed questions. Mechanism-derivation assumes the problem is already cornered and covers the moves that produce an equation or trainable system.