agentsclimarketplace

Alethic derive

Skill hyperion-git/alethic/skills/alethic-derive

Derive a physics result using Generate-Verify-Revise loop with decoupled verificationFrom its SKILL.md

Install
npx -y skills add hyperion-git/alethic --skill alethic-derive

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

One thing to look at

  • 2 stars2 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.

SKILL.md

6.2 KB, as published. Nobody here has run it

/alethic-derive — Alethic Physics Derivation Agent

The user's input is: $ARGUMENTS

Domain Configuration

KeyValue
domainphysics
commandderive
nounderivation
verbderive
agent_titlePhysics Derivation
session_skillalethic-derive
strategy_reset_addendum(from "Strategy Reset Addendum" section below)
disproof_addendum(from "Disproof Escalation Addendum" section below)
adversarial_verifiertrue for thorough/extreme presets; false otherwise — enables 5-round adversarial self-correction in all verifier Task calls
adversarial_breakertrue for thorough/extreme presets; false otherwise — enables adversarial breaker probe on CORRECT verdicts

Balanced Approach Addendum

Append this to the Generator's user message (unless --no-balanced is set):

  1. Check limiting cases and dimensions (balanced approach). Before committing to a derivation approach, check dimensional consistency of the expected result and verify at least one known limiting case (e.g., ħ→0 classical limit, c→∞ non-relativistic limit, weak-coupling limit). Also consider whether the problem's premise might be flawed — does it contradict known physical principles? If so, present the contradiction. Otherwise, proceed with the derivation.

Strategy Reset Addendum

Injected into the Generator prompt (replacing the standard failed_approaches block) when a stall reset is triggered. The {failed_approaches} placeholder is filled by the orchestrator.

STRATEGY RESET — Previous approaches exhausted

The derivation strategies listed below have been attempted and FAILED. You are FORBIDDEN from using them.

{failed_approaches}

For each strategy above: DO NOT use it. DO NOT adapt it. DO NOT build on it. If your plan uses any of these strategies, you MUST change your plan. Reflect on your approach — if it resembles any of the above, choose a different one.

You MUST use a categorically different derivation technique. Start from a completely different physical or mathematical foundation. Consider approaches from a different formalism entirely (e.g., if Lagrangian methods failed, try Hamiltonian; if perturbation theory failed, try exact methods or symmetry arguments).

Disproof Escalation Addendum

Appended to the reset context by the orchestrator when accumulated evidence suggests the claimed result may be incorrect (error category false_premise/interpretation/counterexample, or two consecutive UNSOLVED verdicts).

DISPROOF ESCALATION — Consider that the physical claim may be incorrect

Previous iterations have repeatedly failed to derive this result. Based on accumulated evidence, there is a meaningful probability that the claimed result is INCORRECT.

In addition to exploring categorically different derivation techniques, you MUST also:

  1. Check dimensional consistency: Does the claimed result have correct dimensions? Verify with sympy.physics.units or scipy.constants.

  2. Test limiting cases: Does the result reduce correctly in known limits? (hbar->0 for classical, c->inf for non-relativistic, T->0 for ground state, etc.)

  3. Compare with established results: Does this claim contradict known physical principles, conservation laws, or experimental data?

  4. Numerical estimation: Compute an order-of-magnitude estimate. Does the claimed value match known experimental values?

If you find evidence the claim is false, present a clear disproof:

  • Identify the specific physical principle, limiting case, or data point that contradicts it
  • Verify computationally using Python code
  • Explain the correct result if you can determine it

Examples

  • /alethic-derive "Derive the energy spectrum of the quantum harmonic oscillator" — defaults (5 iter, 3 rev, 50 budget)
  • /alethic-derive -p quick "Derive the classical period of a simple pendulum" — quick preset
  • /alethic-derive -p thorough "Derive the hydrogen atom energy spectrum from the Schrodinger equation" — thorough preset
  • /alethic-derive -p quick -i 4 "Show that F=ma follows from the Lagrangian" — quick preset with iteration override
  • /alethic-derive -i 8 -r 5 "Derive the Dirac equation from relativistic quantum mechanics" — extended
  • /alethic-derive -t 0.95 "Derive Maxwell's equations from the electromagnetic action" — stricter threshold
  • /alethic-derive -B 3 "Derive the hydrogen atom energy spectrum" — 3 candidates per iteration
  • /alethic-derive --textbook "Derive the energy spectrum of the quantum harmonic oscillator" — textbook-style output
  • /alethic-derive -p thorough --textbook "Derive the hydrogen atom energy spectrum" — thorough + textbook
  • /alethic-derive --no-balanced "Derive the Euler-Lagrange equations" — skip dimensional check
  • /alethic-derive --resume .alethic/session-id/ "original problem" — resume from checkpoint
  • /alethic-derive --file problem.md — read problem from file
  • /alethic-derive -q -p thorough "Derive the hydrogen atom energy spectrum" — quiet mode (no dashboard)
  • /alethic-derive --json "Derive the period of a simple pendulum" — JSON output
  • /alethic-derive --model sonnet "Derive Maxwell's equations" — use Sonnet for sub-agents

Load Orchestrator

  1. Find the orchestrator:

    ORCH=$(find ~/.claude/plugins -name "orchestrator.md" -path "*/alethic-common/*" 2>/dev/null | head -1)
    echo "ORCHESTRATOR: $ORCH"
    

    If not found, check the local development path:

    ORCH=$(find /home -maxdepth 6 -name "orchestrator.md" -path "*/alethic-common/*" 2>/dev/null | head -1)
    echo "ORCHESTRATOR: $ORCH"
    
  2. Derive the references directory:

    REF_DIR=$(echo "$ORCH" | sed "s|alethic-common/orchestrator.md|alethic-derive/references|")
    echo "REFERENCES: $REF_DIR"
    
  3. Read the orchestrator file at the path found above.

  4. Follow the orchestrator instructions exactly, using this skill's Domain Configuration, Balanced Approach Addendum, and references directory.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.