docs: add uv and deno agent skills

[enyst]

Summary

Adds two new agent skills in the Agentskill format:

• uv: common project/dependency/env operations for uv (includes note: "If the project uses uv, use this skill")
• deno: common project/dependency/task/tooling operations for Deno (includes note: "If the project uses deno, use this skill")

Each skill includes a references/ directory with links to the official documentation.

Closes #1522.

@enyst can click here to continue refining the PR

[openhands-ai]

Looks like there are a few issues preventing this PR from being merged!

• GitHub Actions are failing:
  • Check README.md in Skills

If you'd like me to help, just leave a comment, like

@OpenHands please fix the failing actions on PR #43 at branch `openhands/skills-uv-deno`

Feel free to include any additional details that might help me get this PR into a better state.

_{^{You can manage your notification settings}}

[enyst]

@OpenHands Read these skills and a README.md in each skill directory as appropriate.

Once you did that (commit and push), then take a deep breath and do a /codereview-roasted . During the review, do all you want to do, and also, in addition, make sure to check the references and make sure they're up to date (we don't want to include outdated info)

Post your review on github as a PR comment. Note that it will be rendered as markdown.

[openhands-ai]

I'm on it! enyst can track my progress at all-hands.dev

[enyst]

Taste Rating

🟡 Acceptable — the skills are small and pragmatic, and the refs are current. But there are a couple of “this is going to bite someone later” rough edges.

---

[CRITICAL ISSUES]

None. Nothing here looks like it’ll break existing userspace.

---

[IMPROVEMENT OPPORTUNITIES]

1) uv skill: you’re recommending curl | sh with zero caveats

• [skills/uv/SKILL.md, Installation section]
• This repo is literally a “skills” library that other agents will blindly follow. Teaching them to pipe arbitrary internet bytes into a shell is… not great.
• Suggestion: keep the install snippet if you must, but add a one-liner caveat like: “Prefer distro packages / verify the installer when possible” and/or link to Astral’s official install page (you already do in references).

2) uv venv --python 3.13 is an oddly specific example

• [skills/uv/SKILL.md, “Create / use a virtual environment”]
• Hard-coding 3.13 reads like “this is the right version”, when in reality it’s “whatever the project uses”. If a repo targets 3.10/3.11, an agent may cargo-cult 3.13 and cause subtle incompatibilities.
• Suggestion: use --python 3.11 only if this org standardizes on it, otherwise write --python 3.x / “match pyproject.toml / CI”.

3) Deno global install example is missing permission intent

• [skills/deno/SKILL.md, “Install globally”]
• deno install -g -N -R … is fine, but it’s not obvious to readers what -N and -R are doing without context (network/read allowlists). This is exactly where people accidentally grant too much.
• Suggestion: add a short note: “choose the minimal permissions at install time; avoid blanket flags unless needed”.

4) References: good, but a tiny bit “link farm”

• [skills/*/references/README.md]
• Links are up-to-date (all return HTTP 200 as of 2026-02-14), but some are redundant. For example, pointing to cli/ plus every subcommand page is overkill unless you’re explicitly trying to ensure coverage.
• Suggestion: consider keeping 2–4 “anchor” docs per skill: overview, CLI reference, dependency management, and one “security/permissions” doc (for Deno).

---

[STYLE NOTES]

5) Triggers are a bit weak for Deno

• [skills/deno/SKILL.md, frontmatter triggers]
• Only deno means you might miss obvious signals like deno.json, deno.jsonc, deno.lock.
• Suggestion: add triggers for deno.json, deno.jsonc, deno.lock.

---

VERDICT

✅ Worth merging once the curl|sh guidance is made slightly less “teach agents unsafe habits”. Everything else is cleanup-level.

KEY INSIGHT

These skills are basically “golden path instructions” for autonomous agents — treat them like you’re writing security-sensitive runbooks, not a personal cheat sheet.

[enyst]

Follow-up: pushed 0843b86 addressing all review items.

• Added explicit caveats around curl | sh in the uv install section
• Removed the overly-specific uv venv --python 3.13 example in favor of matching project constraints
• Clarified Deno global install permission intent
• Expanded Deno triggers (deno.json, deno.jsonc, deno.lock)
• Trimmed references to a smaller set of anchor docs (all links still current).