How do I install the Julia Package Dev skill?

Run npx skillmds@latest add tomevault-io/julia-package-dev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Julia Package Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Julia Package Dev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Julia Package Dev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Julia Package Dev?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Julia Package Dev by tomevault-io — Agent Skill

Name: Julia Package Dev
Author: tomevault-io

Julia Package Dev

Create and develop Julia packages in local environments, including package bootstrapping, multi-package workspaces, package extensions, and Pkg apps. Use when starting a package or managing package environments, dependencies, structure, and related development workflows. Use when this capability is needed.

tomevault-io d4782cc 2 files · 3.8 KB Updated Sep 17, 2026

File contents

Julia Package Development

Use this skill for package-oriented Julia work: bootstrapping a package, local environments, multi-package workspaces, extensions, and Pkg apps.

Core Workflow

using Pkg

Pkg.activate("./dev")
Pkg.develop(path="./MyPackage.jl")
using MyPackage

Prefer environments over mutating the global default environment.

Set ENV["JULIA_PKG_SERVER_REGISTRY_PREFERENCE"] = "eager" before Pkg operations in local or CI sessions in this workspace. Use this by default when recent registrations may matter; otherwise just-registered packages can appear to be missing and create false resolution failures.
Prefer Pkg.test(...) over directly executing test/runtests.jl when validating a package checkout. Treat direct test/runtests.jl execution as a runner-debugging path, not the default validation path.
Never read or edit Manifest.toml directly. Treat every manifest as generated state owned by Pkg.
If dependency resolution behaves impossibly, run Pkg.update() and Pkg.resolve() in the relevant environment first. If recurrent issues remain, delete the relevant Manifest.toml file and regenerate it with Pkg.instantiate().
Read Project.toml when needed, but change dependencies and compat entries only through Pkg APIs such as Pkg.add, Pkg.develop, Pkg.rm, Pkg.free, and Pkg.compat.

Multi-Repo Rule

In a workspace with sibling repos, if compat or registry resolution blocks testing, first Pkg.develop(path=...) the local dependency checkouts already present, preferably on their current master/main.
Do this before chasing registry lag or editing compat blindly.

Pick a Topic

Pkg commands and dependency management: references/pkg-commands.md
Interactive debugging and exploration: references/debugging.md
Multi-package development and release flow: references/multipackage-git-workflow.md
Package extension patterns: references/extension-patterns.md
Testing and documenting extensions: references/extension-testing.md
User-facing extension error hints: references/weakdephelpers.md
Pkg app scaffolding and CLI patterns: references/pkg-app-patterns.md

Common Tasks

Shared Workspace

using Pkg
Pkg.activate("quantum-dev")
Pkg.develop(path="./QuantumInterface.jl")
Pkg.develop(path="./QuantumSavory.jl")

Notes

Use julia-tests for test execution and organization.
Use julia-docs for docs setup and doctests.
Use julia-comonicon when you need a richer CLI than Pkg apps provide.

Related Skills

julia-tests
julia-docs
julia-scratch

Source: krastanov/juliallmagentskills — distributed by TomeVault.

---name: julia-package-devdescription: Create and develop Julia packages in local environments, including package bootstrapping, multi-package workspaces, package extensions, and Pkg apps. Use when starting a package or managing package environments, dependencies, structure, and related development workflows. Use when this capability is needed.---# Julia Package DevelopmentUse this skill for package-oriented Julia work: bootstrapping a package,local environments, multi-package workspaces, extensions, and Pkg apps.## Core Workflow```juliausing PkgPkg.activate("./dev")Pkg.develop(path="./MyPackage.jl")using MyPackage```Prefer environments over mutating the global default environment.- Set `ENV["JULIA_PKG_SERVER_REGISTRY_PREFERENCE"] = "eager"` before `Pkg` operations in local or CI sessions in this workspace. Use this by default when recent registrations may matter; otherwise just-registered packages can appear to be missing and create false resolution failures.- Prefer `Pkg.test(...)` over directly executing `test/runtests.jl` when validating a package checkout. Treat direct `test/runtests.jl` execution as a runner-debugging path, not the default validation path.- Never read or edit `Manifest.toml` directly. Treat every manifest as generated state owned by `Pkg`.- If dependency resolution behaves impossibly, run `Pkg.update()` and `Pkg.resolve()` in the relevant environment first. If recurrent issues remain, delete the relevant `Manifest.toml` file and regenerate it with `Pkg.instantiate()`.- Read `Project.toml` when needed, but change dependencies and compat entries only through `Pkg` APIs such as `Pkg.add`, `Pkg.develop`, `Pkg.rm`, `Pkg.free`, and `Pkg.compat`.## Multi-Repo Rule- In a workspace with sibling repos, if compat or registry resolution blocks testing, first `Pkg.develop(path=...)` the local dependency checkouts already present, preferably on their current `master`/`main`.- Do this before chasing registry lag or editing compat blindly.## Pick a Topic- Pkg commands and dependency management: `references/pkg-commands.md`- Interactive debugging and exploration: `references/debugging.md`- Multi-package development and release flow: `references/multipackage-git-workflow.md`- Package extension patterns: `references/extension-patterns.md`- Testing and documenting extensions: `references/extension-testing.md`- User-facing extension error hints: `references/weakdephelpers.md`- Pkg app scaffolding and CLI patterns: `references/pkg-app-patterns.md`## Common Tasks### Shared Workspace```juliausing PkgPkg.activate("quantum-dev")Pkg.develop(path="./QuantumInterface.jl")Pkg.develop(path="./QuantumSavory.jl")```## Notes- Use `julia-tests` for test execution and organization.- Use `julia-docs` for docs setup and doctests.- Use `julia-comonicon` when you need a richer CLI than Pkg apps provide.## Related Skills- `julia-tests`- `julia-docs`- `julia-scratch`---> Source: [krastanov/juliallmagentskills](https://github.com/krastanov/juliallmagentskills) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions