CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dep-radar

Load to run or tune a dependency sweep.

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/dep-radar/SKILL.md
SKILL.md
Quality
Evals
Security

Project Instructions

Problems with a kendex-owned skill go through kendex report; check ownership in the file first.

dep-radar

inventory → detect → research → classify → upgrade-with-fixes → report the owner tier.

Generic engine only: concrete package names, pinned binaries, and fork lists live in the per-repo inventory, never here.

Load github before workflows/sweep.md § Phase 4 (PR creation, CI status, merges). Load worktree when a run applies more than one surface, one working copy per surface branch.

Operating policy (the contract with the product owner)

Rule keys are the contract; an inventory owner-rule cites them. Dropping or renaming a key changes the contract.

RuleContract
auto-with-fixesThe default. Security fixes; patch/minor bumps; pinned-binary version+SHA refreshes from OFFICIAL manifests only; SDK, agent-tooling, and runtime-binary bumps and npm/cargo majors, doing the bump AND fixing its fallout (API migrations, re-vendored bundled-extension bridges, tests, CI) in the SAME per-surface workstream; bundled-extension fork updates and local patch rebases when the consuming repo's full test suite gates the sync.
report-never-autoModel-weight swaps; changes to durable/recorded data scope; anything an inventory owner-rule explicitly demotes. Nothing else is report-by-default.
uncertainAttempt the upgrade; report only what actually failed, with error output.
deferOnly on a strong concrete blocker you actually hit, such as a dropped capability with no migration path or a transitive that does not support the new version. Never a generic "it's a major" risk or any other anticipated one.
one-pr-per-surfaceOne PR per surface; never batch surfaces. A surface's fallout fixes go in THAT surface's PR.
upstream-check-requiredEvery pinned surface must have a wired upstream check command; a surface lacking one is an inventory defect the run must fix.
dated-reportEvery run ends with a dated report.
demote-onlyInventory owner-rules may demote auto→report, never promote report→auto.

Sweep

When running a dependency sweep, follow workflows/sweep.md.

Technology playbooks

The inventory records which apply and every concrete package, binary, and fork name.

SurfaceUpstream checkTier and handlingVerify
Pinned AI/agent SDKRegistry latest + release notesAuto-with-fixes, majors included: migrate changed auth, runtime, and tooling APIs in the same PR. New provider models a bump exposes are report-tier; the bump itself ships.Build + test suites; confirm expected models and features appear
Pinned runtime binary with SHA constantsOfficial release manifest for the exact version, never a third party, never hand-computed from a local download aloneAuto-with-fixes: migrate auth, protocol, and contract changesPin unit tests + a live download smoke on the host platform
npm/pnpm depspnpm -r outdated, pnpm auditAuto-with-fixes, including majors: fix the mechanical fallout (renamed APIs, config, broken tests) in the same PRTypecheck + tests
cargo depscargo update --dry-run, cargo audit when installedAuto-with-fixes, including majorsWorkspace tests at the repo's CI feature parity
Bundled-extension forks, a small upstream synced in by script, provenance tracked, local patches on topThe sync script's upstream refAuto-with-fixes only when the consuming repo's full test suite gates the sync: take the update, rebase the local patches, fix fallout in the same PR.That full test suite plus the sync script's own checks
Patched vendor forks of large upstreams, with no script-gated syncUpstream releasesReport, owner-decidednone
Model weights and artifact SHA pinsUpstream manifestReport, never swap weights automaticallyThe repo's own integrity-verify scripts
Pinned GitHub Actions SHAsTag → SHA for the same actionAuto for patch/minor tag moves, refreshing the SHA comment too; majors auto-with-fixes, migrating the workflow in the same PRWorkflow run

Guardrails

  • Migration-bearing dep bumps (DB or storage tooling) carry merge-order and version-gap hazards; check the repo's before merging.
  • Shell commands follow orch SKILL.md § Harness-Safe Shell.
Repository

vanillagreencom/kendex

Path

.agents/skills/dep-radar/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.