Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    18 — Unlikely Bridgewright · Complete Edition

    1

    Keeps falsifiable cross-domain prototypes and bridge testing, adding everyday experiments such as applying manufacturing materials planning to a pantry.

    $25

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    18 — Unlikely Bridgewright · Complete Edition

    18 — Unlikely Bridgewright · Complete Edition

    Example session with this skill installed

    Everyday request

    Can the bill-of-materials idea from manufacturing help me plan three batches of food from my pantry? Build a small example and show exactly what I still need.

    For a reproducible local example, use the included synthetic structured fixture:

    {
      "batches": 3,
      "requirements": [
        {
          "id": "flour",
          "quantity": 2,
          "unit": "cups"
        },
        {
          "id": "sugar",
          "quantity": 1,
          "unit": "cups"
        }
      ],
      "stock": [
        {
          "id": "flour",
          "quantity": 4,
          "unit": "cups"
        },
        {
          "id": "sugar",
          "quantity": 3,
          "unit": "cups"
        }
      ]
    }
    

    Run the class's packaged helper on that fixture. Show the readable result, full structured output, executed Thirsty calculation and the limits of what was demonstrated.

    • Read your context and instructions
    • Compiled the output

    Unlikely Bridgewright — real local worked example

    Example type: Actual execution of the packaged structured helper on synthetic input. This is not a claimed live customer session or a full specialist-model benchmark.

    Readable work product

    Materials plan:
    - flour: need 6 cups, have 4, short 2
    - sugar: need 3 cups, have 3, short 0
    Manufacturing bill-of-materials pattern applied to a household or project recipe; no substitutions or unit conversions assumed
    

    Complete structured result

    {
      "materials_plan": [
        {
          "available": 4,
          "id": "flour",
          "required": 6,
          "shortfall": 2,
          "status": "calculated",
          "unit": "cups"
        },
        {
          "available": 3,
          "id": "sugar",
          "required": 3,
          "shortfall": 0,
          "status": "calculated",
          "unit": "cups"
        }
      ],
      "transfer": "Manufacturing bill-of-materials pattern applied to a household or project recipe; no substitutions or unit conversions assumed"
    }
    

    Executed Thirsty-lang calculation

    module conclave: core
    
    drink result = 1
    pour result
    

    The helper checked the language result independently, encoded the complete structured result using the published TSCG-B codec, decoded it and compared the text. Running the standalone helper generates the result files and execution receipt. The example shown here was produced on the supplied synthetic input.

    The deeper specialist use

    Request: Use a manufacturing bill-of-materials pattern to plan three batches from pantry stock. Each batch needs two cups of flour and one cup of sugar; stock is four cups and three cups.

    Illustrative specialist response: The correspondence is explicit: product recipe → batch requirements; inventory → pantry stock; materials shortage → shopping shortfall. Three batches need six cups of flour and three cups of sugar, leaving a flour shortfall of two cups and no sugar shortfall. Do not subtract grams from cups without an agreed conversion. The working specimen tests a useful mechanism transferred between domains; it makes no claim of universal novelty.

    The preceding specialist response is an authored illustration, not an executed external action. The original class procedures and supporting skills remain included for an actual authorized assignment.

    Next step

    Replace the fixture with your own task data after checking that it fits the helper's input model, or use the conversational workflow directly with your AI host. Use a fresh output directory; the helper refuses to overwrite an existing result. Review factual classifications and missing inputs before relying on the result.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Unlikely Bridgewright — Complete Edition

    Take the strange connection far enough to test it.

    Keeps falsifiable cross-domain prototypes and bridge testing, adding everyday experiments such as applying manufacturing materials planning to a pantry.

    One class. 47 equipped skills. The original specialist method plus six practical everyday workflows. $25 as a one-time purchase.

    For creative problem-solving, small prototypes and turning a clever analogy into a practical tool. For deeper work, the class retains its original specialist equipment and source-defined method: Can an unusual cross-domain correspondence support a falsifiable implementation?

    What you actually receive

    • All 40 original skills, including the specialist entrypoint, original supporting procedures, language workbench and evaluation lab.
    • Six added everyday skills, listed in full below, and the new structured helper and worked example.
    • 1 restored named dependency/dependencies: epistemic-status-enforcer.
    • Class methods, contracts, source references, standalone task-packet tooling, executable helpers and worked examples, delivered through your connected AI.
    • Standalone Thirsty-lang and TSCG-B tooling that uses the real thirsty-lang==0.9.0 runtime. Code execution requires Python 3.10+, a host execution tool and that separately installed package in the same environment. No runtime wheel is delivered through Agensi.

    The specialist class: the original depth stays equipped

    1. Extract explicitly supported structures and operations from each source.
    2. Propose a correspondence with mismatches and counterexamples alongside it.
    3. Separate metaphor from candidate transferable mechanism.
    4. Define a small falsifiable experiment and precommit its acceptance condition.
    5. Build the candidate in the bounded prototype workspace using an approved toolchain.
    6. Run positive, negative and adversarial examples; retain failures.
    7. Return the working specimen or failed hypothesis with precise applicability limits.

    Specialist deliverable: bridge_specimen. Its source-defined result fields are source_correspondence, differences, hypothesis, experiment, prototype_artifacts, observed_results. These guide the work product; an actual outcome requires the task inputs, authorized tools and evidence.

    Six everyday workflows — the documented practical use cases

    1. Apply a materials plan to a household recipe

    Treat recipe quantities as requirements and stock as inventory. Scale by batch count, compare compatible units and flag mismatches instead of inventing conversions.

    2. Turn an interesting analogy into a testable idea

    Name the source mechanism, the target problem, matching structures and mismatches. Define one experiment that could reject the idea.

    3. Find where a borrowed pattern actually fits

    Compare operations and constraints rather than superficial vocabulary. Retain counterexamples and explain what does not transfer.

    4. Build the smallest useful version of a borrowed mechanism

    Specify inputs and outputs, build in an isolated candidate folder, run positive and negative cases, and show a working artifact or the failed hypothesis.

    5. Create a new workflow from a tested correspondence

    Combine only mechanisms supported by the supplied evidence, name new assumptions, and compare the candidate to the existing workflow.

    6. Decide whether a prototype is worth continuing

    Review actual outcomes, integration cost and failure cases. Recommend continuation only within the demonstrated scope; do not claim universal novelty.

    Example 1 — what a specialist assignment can look like

    You ask: Use a manufacturing bill-of-materials pattern to plan three batches from pantry stock. Each batch needs two cups of flour and one cup of sugar; stock is four cups and three cups.

    Illustrative response: The correspondence is explicit: product recipe → batch requirements; inventory → pantry stock; materials shortage → shopping shortfall. Three batches need six cups of flour and three cups of sugar, leaving a flour shortfall of two cups and no sugar shortfall. Do not subtract grams from cups without an agreed conversion. The working specimen tests a useful mechanism transferred between domains; it makes no claim of universal novelty.

    This example illustrates the class method. It is not an assertion that the proposed external investigation, model trial or system change has been executed.

    Example 2 — an everyday request

    Can the bill-of-materials idea from manufacturing help me plan three batches of food from my pantry? Build a small example and show exactly what I still need.

    The work product: An explicit cross-domain mapping, a small executable specimen, limits, and a result that can be checked.

    The included local helper demonstrates a bounded part of this workflow. Its actual run on synthetic structured input produced:

    Materials plan:
    - flour: need 6 cups, have 4, short 2
    - sugar: need 3 cups, have 3, short 0
    Manufacturing bill-of-materials pattern applied to a household or project recipe; no substitutions or unit conversions assumed
    

    See the demo section below for its complete input, structured result and executed Thirsty calculation.

    Example 3 — using the class template on your own material

    Use Unlikely Bridgewright — Complete Edition.
    Goal: [the concrete result I need]
    Material: [paste or attach the actual records, notes, code or facts]
    Scope: [what may be inspected or changed]
    Constraints: [time window, dependencies, formats and important conditions]
    Deliver: An explicit cross-domain mapping, a small executable specimen, limits, and a result that can be checked.
    Use the original specialist method when the problem requires it.
    Ask only for missing facts that materially change the result.
    Show what you actually did and what still needs a decision.
    

    For a simple request, use only the relevant everyday mode. For advanced work, select the original specialist procedures. Keeping the equipment available does not require loading every skill into every interaction.

    Every skill available in this pack (47 total)

    • architecture-decision-recorder — Edition XXII source-attributed supplemental agent procedure: Architecture choice and tradeoff recording.

    • build-reproducibility-receipts — Create verifiable local build and test receipts linking source snapshots, commands and exact artifact bytes.

    • ceta-class-router — Choose a Thirstforged Conclave sub-agent class for a CETA task, prepare its bounded assignment and exact skill inventory, and distinguish instruction packets from native profile activation.

    • ceta-cross-representation-meaning-trials — Test whether intent, obligations, schemas, UTF representations, and implementation preserve the same supported meaning, including negative and ambiguous cases.

    • ceta-evidence-cross-examination — Cross-examine a Thirstforged Conclave result against raw observations, exact source bindings, expected predicates, and actual reviewer identity before integration.

    • ceta-incentive-failure-societies — Run bounded deterministic agent-society simulations that expose incentive conflicts, metric gaming, missing stakeholders, and collective failure despite local compliance.

    • ceta-rare-failure-cultivation — Search reproducible crash, cancellation, delay, ordering, and partial-progress schedules in disposable fixtures to expose rare CETA failures.

    • ceta-resource-pressure-reduction — Minimize a discovered fault or resource-pressure failure into a reproducible causal case while preserving measurement provenance and uncertainty.

    • ceta-utf-contract-map — Map a CETA task to the six Universal Thirsty Family tiers and exact isolated Thirsty-Lang 0.9.0 tools, preserving the difference between analysis, integrity, and authority.

    • codex-acceptance-crosswalk — Use for map source-defined requirements to executable acceptance evidence.

    • codex-approval-trace — Use for trace decision, requester, scope, expiry, and evidence receipts.

    • codex-autonomy-review — Use for evaluate competence evidence and legitimate authority for autonomy changes.

    • codex-build-reproducer — Use for inventory local build ingredients and reproducibility conditions.

    • codex-ci-release-gate — Use for check ci test and dependency inputs before claiming release readiness.

    • codex-claim-integrity — Use for prevent observed/inferred/proposed/implemented states from being conflated.

    • codex-conversation-fidelity — Use for audit attribution and interpret the actual speaker words without invented states.

    • codex-deployment-readiness — Use for review deploy artifacts and recovery preconditions; never assert deployment.

    • codex-dialogue-fidelity — Use for examine dialogue against literal commitments and actual word senses.

    • codex-evidence-ledger — Use for validate referenced evidence paths and source identity.

    • codex-failure-reproducer — Use for create reproducibility inputs from logs and source; do not invent successful runs.

    • codex-hostile-review — Use for challenge the implementation for bypass, risk, and missing negative evidence.

    • codex-implementation-planner — Use for turn the owner's stated task into a smallest-complete-fix plan.

    • codex-operations-support — Use for diagnose support cases using actual logs and local help documentation.

    • codex-repo-preservation — Use for protect untracked work, check provenance and refuse destructive cleanup.

    • codex-scope-guardian — Use for prevent invented or silently widened objectives and repository scope.

    • codex-source-integrity — Use for check bundled source document checksums and protect observed provenance.

    • conclave-evaluation-lab — Design held-out comparisons of the equipped agent and baseline workflows with matched models, tools, budgets, and recorded evidence.

    • conclave-language-workbench — Use Thirsty-lang as the primary local language and TSCG-B to encode/decode exact UTF-8 task and result text.

    • conclave-unlikely-bridgewright — Keeps falsifiable cross-domain prototypes and bridge testing, adding everyday experiments such as applying manufacturing materials planning to a pantry.

    • epistemic-status-enforcer — Apply explicit epistemic status to meaningful claims.

    • polyglot-differential-tests — Verify that implementations in different languages produce equivalent results for the same contract.

    • polyglot-ffi-bridge — Build and test native foreign-function interfaces across C, Rust, Python, C++, C# and other runtimes.

    • polyglot-process-bridge — Implement a robust polyglot subprocess protocol using stdin/stdout, JSON Lines, structured errors, timeouts and shutdown.

    • polyglot-schema-contracts — Create executable versioned data contracts across multiple programming languages.

    • polyglot-stack-selector — Select practical combinations of programming languages and runtime boundaries for one application.

    • polyglot-wasm-bridge — Build WebAssembly language bridges for browser or WASI hosts.

    • proof-obligation-generator — Edition XXII source-attributed supplemental agent procedure: Execution proof obligation construction.

    • property-fuzz-test-engineer — Implement executable property-based tests, deterministic fuzz harnesses and failure minimization for source code.

    • python-production-coder — Implement and repair working Python applications, libraries and asynchronous services.

    • thirsty-work-orchestrator — Edition XXII source-attributed supplemental agent procedure: Role graph scheduling and evidence handoff.

    • type-contract-architect — Create implementable domain types and API contracts before coding.

    • unlikely-bridgewright-bridge-review — Decide whether a prototype is worth continuing.

    • unlikely-bridgewright-cross-domain-map — Find where a borrowed pattern actually fits.

    • unlikely-bridgewright-idea-to-experiment — Turn an interesting analogy into a testable idea.

    • unlikely-bridgewright-pantry-as-materials — Apply a materials plan to a household recipe.

    • unlikely-bridgewright-process-invention — Create a new workflow from a tested correspondence.

    • unlikely-bridgewright-small-prototype — Build the smallest useful version of a borrowed mechanism.

    Thirsty-lang and TSCG-B in practice

    Run the packaged helper with Python 3.10+ to generate a readable result, structured JSON, the executed .thirsty calculation, a binary .tscg-b result and an execution receipt. The helper executes supported arithmetic in Thirsty-lang and independently checks the result; Python handles structured input and the domain algorithm. TSCG-B preserves result text through binary encode/decode. A valid frame does not itself prove the text is true or authorize an action.

    Preservation and validation

    Every original skill identity and the specialist methods remain, together with the six everyday additions and repaired named dependencies. The Agensi upload layout adapts executable scripts and reference delivery; historical source files and preservation records remain in the creator's original archive.

    The repaired collection passed 409 local delivery and execution checks, including all 19 standalone class helpers, real Thirsty-lang calculations, TSCG-B round trips, exact task packets, delivery limits and negative cases. Independent checks also passed all 52 distinct audit-tool bindings and their source-index lookups. Six compiler-specific examples were not executed because their compiler dependencies were absent. These results do not establish every AI host's behavior, marketplace approval, live buyer retrieval, frontier-model superiority or revenue.

    Start using it

    Connect your AI to Agensi and ask: “Use my Agensi skill 18 — Unlikely Bridgewright · Complete Edition. My goal is [result]. Here is my actual material: [notes, records or code].” The pack provides an index; your AI loads the class entrypoint skills/conclave-unlikely-bridgewright/SKILL.md, then loads the supporting skills relevant to your task. Purchasing the pack does not automatically run all its skills at once.

    Text and reasoning workflows run through your existing AI. Standalone scripts additionally require Python 3.10+ and a code execution tool. Thirsty-lang and TSCG-B execution requires thirsty-lang==0.9.0 installed separately in that environment; your AI should explain missing requirements before starting. Scripts are fetched unchanged through Agensi, executed temporarily and removed. Task result files can be delivered to you; the purchased skill is not installed as a downloadable local folder.

    Image, video, voice and data services from Agensi's optional tools catalog are separate paid services. This pack does not require adding those services merely to use its text workflows or Python helpers. External actions, compiler tasks and account access still require the actual relevant host tools and your permission.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Research & Analysis.

    This is a skill/class package for an existing compatible AI host. It does not supply model weights, hosted compute, API credits, automatic account connections or permissions. The included helpers accept bounded structured inputs; they are not general document parsers or substitutes for semantic review. Their actual synthetic-fixture outputs are distinguished from authored specialist illustrations. Local preservation/tool checks do not establish correctness on arbitrary tasks, frontier-model superiority, customer results or revenue. Optional UTF analysis features may require additional dependencies. Marketplace ingestion of the final multi-skill ZIP remains subject to the receiving platform’s actual review.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Software
    Node.js
    Optional
    Python 3.10+thirsty-lang==0.9.0

    Text workflows use your connected AI. Code needs Python 3.10+ and an execution tool. Thirsty-lang and TSCG-B need thirsty-lang==0.9.0 installed in that environment. No hosted model or API credits are included.

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Read Files, Write Files and Terminal/Shell support the optional local examples and authorized project work. Work stays within the user-approved scope. Browser, network, services and credentials are task-dependent and are not granted by this package. A draft, recommendation or prepared payload is not evidence of an external action.

    Listed5 days ago

    What's inside

    Frequently Asked Questions

    This listing is for Unlikely Bridgewright — Complete Edition: one specialist class package with 47 skills, all 40 original skills retained, six added everyday workflows, repaired named dependencies, tools, references and worked examples. It is a one-time purchase, not a monthly subscription. Host-model usage and third-party service charges are separate.

    Every original skill identity and specialist procedure remains, with six everyday additions. Executable helpers and reference layout were adapted for Agensi temporary-file delivery. The creator retains the historical sources and preservation records separately.

    For creative problem-solving, small prototypes and turning a clever analogy into a practical tool. The everyday modes can be used conversationally with supplied notes, facts or records. Advanced technical tasks and executable utilities require the relevant tools and environment.

    Connect your AI to Agensi, ask it to use this pack by name, and provide your actual goal and material. It loads the class entrypoint and then the supporting skills needed for the task. The pack is selected on demand; all skills do not run automatically at purchase.

    The structured helper example was actually executed on synthetic input, with real Thirsty-lang execution and a TSCG-B round trip. Running the helper generates result files and a receipt. The specialist scenario is labeled illustrative. No live customer outcome, marketplace buyer test or unrun model benchmark is claimed.

    This purchase supplies the listed class package for an existing compatible AI host. It does not supply model weights, hosted compute, API credits or all 19 Conclave agents. Other class packages are separate.

    Text workflows use the connected AI. Script execution needs Python and an execution tool; language and codec operations additionally need thirsty-lang==0.9.0. No bundled binary runtime, model, API credits or automatic account connections are supplied. Advanced tasks need the relevant compiler, browser, file or account tools and your permission. The pack itself grants none of those tools.

    New in Research & Analysis