Skip to content
cccskills
FreePublished on GitHub

generating-julia-package

Create a Julia project environment for scripts that use external libraries, or set up a reusable package with its project metadata and module file. The skill covers the default in-place layout and an explicitly requested subdirectory layout.

OriginalShow the original description

Use when you create a JuliaLang package

hashgraph-online/awesome-codex-plugins1,422 stars(GitHub 1,422 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Setting up dependencies for a Julia script
  • Creating a reusable Julia package
  • Choosing a package directory layout
  • Verifying that a new Julia package loads

Files included (1)

  • SKILL.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Creating a Julia Package

Project Environment

If you want to create a simple script that depends on external libraries, you should create a "project environment". This means making a Project.toml file like the one below.

[deps]
"<Installed Package 1>" = "<UUID for Installed Package 1>"
"<Installed Package 2>" = "<UUID for Installed Package 2>"
"<Installed Package 3>" = "<UUID for Installed Package 3>"

To install an external library (for example, TargetPackage), run the following in your terminal:

julia --project -e 'using Pkg; Pkg.add("TargetPackage")'

Package Directory

If you want to create a reusable package or a larger scale script, you should create a "package directory".

Choosing the layout

Default: in-place layout. Create ./Project.toml and ./src/MyPkg.jl directly in the current working directory, with no subdirectory named after the package. Use this whenever the user asks to "create a package MyPkg" without further qualification.

Opt-in: subdirectory layout. Only use this when the user explicitly asks for a subdirectory — for example "create the package under a new directory", "サブディレクトリを作って", "MyPkg/ 配下に作って", or when the user is bootstrapping multiple packages side by side under a single workspace and a subdirectory is necessary to disambiguate them.

Do NOT use Pkg.generate("MyPkg") for the in-place layout — it always creates a subdirectory. The in-place layout is the default and must be produced by hand-writing the files (see the steps below).

In-place layout (default, no subdirectory)

To create Project.toml and src/MyPkg.jl directly in the current working directory:

  1. Generate a UUID for the uuid field of Project.toml:

    $ julia -E 'using UUIDs; string(uuid4())'
    "43d6671a-6eab-408d-9ef9-8f584d9146fb" # Example output.
    
  2. Write ./Project.toml with the package name and the UUID from step 1:

    name = "MyPkg"
    uuid = "43d6671a-6eab-408d-9ef9-8f584d9146fb"
    authors = ["Your Name <you@example.com>"]
    version = "0.1.0"
    
  3. Write ./src/MyPkg.jl with the module skeleton:

    module MyPkg
    
    greet() = "Hello"
    
    end # module MyPkg
    
  4. Verify by loading the package from the current directory:

    $ julia --project=. -e 'using MyPkg; println(MyPkg.greet())'
    

Subdirectory layout (opt-in only)

Only use this when the user explicitly asks for it. To create a package named MyPkg under a new subdirectory, run:

$ julia -e 'using Pkg; Pkg.generate("MyPkg")'

This will create:

$ tree
.
└── MyPkg
    ├── Project.toml
    └── src
        └── MyPkg.jl

3 directories, 2 files

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Plan worthwhile local tasks by checking dependencies, effects, resources, and platform boundaries, then execute the exact approved plan. It can use safe parallel work or suitable Apple-silicon backends when the project exposes them.

  • Speed up independent local build or test steps
  • Plan a task with several dependency-linked operations
  • Choose an Apple-silicon backend for supported numerical or media work
hashgraph-online/awesome-codex-plugins1.4KUpdated Oct 27, 2026

add

FreeSummary

Record deferred engineering decisions and temporary workarounds in a debt registry, with context such as effort, ongoing cost, affected area, and payoff trigger. Entries receive short labels so they can be reviewed or dropped later.

  • Logging a TODO or unfinished implementation
  • Recording a temporary default or bypassed check
  • Tracking a swallowed error or loosened type
hashgraph-online/awesome-codex-plugins1.4KUpdated Oct 28, 2026

Generate or compare AI agent code for LangChain, EINO, AutoGen, AgentScope, and CrewAI using framework-specific templates, API mappings, conventions, and project structures. Reference files include verification dates to help identify potentially outdated guidance.

  • Creating an agent project for a chosen framework
  • Comparing APIs across supported agent frameworks
  • Referencing framework-specific tool and memory patterns
hashgraph-online/awesome-codex-plugins1.4KUpdated Oct 26, 2026

Investigate a reproducible bug, test failure, or unexpected page behavior, then make a narrowly scoped fix. The workflow calls for a regression test before changing code, verifies the fix, and reports remaining risks and evidence while avoiding unrelated refactoring or feature work.

  • Finding the cause of a failing test
  • Fixing an unexpected page or feature behavior
  • Adding a regression test before a minimal code change
hashgraph-online/awesome-codex-plugins1.4KUpdated Oct 28, 2026

Build an AI agent project through six collaborative stages, from requirements and architecture to tools, prompts, code generation, and verification. Start framework-independent, then generate a runnable project for frameworks such as LangChain, EINO, AutoGen, AgentScope, or CrewAI.

  • Designing an AI agent from a business need
  • Generating a runnable agent project
  • Planning tools, prompts, and orchestration
hashgraph-online/awesome-codex-plugins1.4KUpdated Oct 26, 2026

Audit a project or learning workflow for scope drift, conflicting plans, inconsistent names, and code quality concerns. The skill reads project files and code, then reports evidence, severity, and suggested next steps without changing files.

  • Checking whether project work has drifted from its agreed scope
  • Finding conflicting plans or inconsistent naming
  • Reviewing code against project decisions without editing it
hashgraph-online/awesome-codex-plugins1.4KUpdated Oct 28, 2026

See all skills by hashgraph-online

Report a problem with this skill