Library · OpenRouter · dependency-upgrade
Dependency Upgrade
Use OpenRouter to upgrade a dependency while controlling compatibility risk, optimized for multi-model production routing.
Id: openrouter/dependency-upgrade · Status: Untested · FREE · Primary action: COPY / USE (not a live RUN claim).
What is this
A FREE OpenRouter resource. Open the full body below, copy it, and use it in a compatible AI surface you control.
What you can do now
Copy the complete instructions and fill in the placeholders ([GOAL], [INPUTS], [CONTEXT_OR_FILES], [CONSTRAINTS]) with your real material.
Full text
Free. No sign-up. The full text is right here. Copy it, or take the file with you.
無料・登録不要。全文はこの下にあります。コピーするか、ファイルで持ち帰れます。
Download .md.md で持ち帰る How to run it動かし方 Fork itフォークする Results & questions結果・質問を書く
You are handling **Dependency Upgrade** in OpenRouter. GOAL [GOAL] INPUTS [INPUTS] CONTEXT / ASSETS [CONTEXT_OR_FILES] CONSTRAINTS [CONSTRAINTS] EXECUTION 1. State the concrete objective and identify only missing information that would make execution unsafe or materially unreliable. Continue without blocking on optional details. 2. Inspect/analyze the supplied context before changing anything or drawing conclusions. 3. Classify before routing; define capability criteria, provider/privacy constraints, required parameters, fallbacks, validation and safe observability. 4. Keep evidence, assumptions and unknowns separate. Never invent files, source facts, tool results, metrics, test results or completed actions. 5. Produce the actual artifact for this task; do not return generic advice about how to do it. 6. Verify the artifact against [CONSTRAINTS] and the requested outcome before returning it. 7. For this use case specifically, ensure the result can upgrade a dependency while controlling compatibility risk and includes concrete validation or acceptance criteria. TARGET-SPECIFIC RULE Prefer capability criteria over hard-coded model names; define fallback triggers and provider/privacy constraints. OUTPUT CONTRACT RESULT: [completed | blocked] DELIVERABLE: [OpenRouter routing policy/request template with classifier, criteria, fallback, privacy, validation and observability] VALIDATION: [checks performed / evidence used] ASSUMPTIONS: [material assumptions only] REMAINING: [none, or exact unresolved issue] PLACEHOLDERS [GOAL] desired outcome [INPUTS] raw task material [CONTEXT_OR_FILES] repository, documents, data, workflow context or API constraints [CONSTRAINTS] scope, format, safety, compatibility, privacy, budget or policy constraints
Original BSV text, MIT License. Use is at your own risk. BSV does not run it for you. What is open here
BSVオリジナルの文面、MITライセンス。 利用は自己責任です。BSVが代わりに実行することはありません。何が開いているか
This job is also written for 7 other tools. See all 8 versions side by side.
この仕事は、ほかに 7 のツール向けの版があります。8 版を並べて見る。
Related FREE resources
- Dependency Upgrade (Cursor)
- Dependency Upgrade (Claude Code)
- Dependency Upgrade (Gemini)
- Repository Onboarding (OpenRouter)
- Feature Implementation (OpenRouter)
- All OpenRouter
Discovery links only — not a claim that BSV executes these together.