agentic-ecology-init
Skill11 starsChanged 2 months agoApache-2.0View on GitHub
Initializes a local uv-managed project directory for agentic ecology workloads. Sets up Python dependencies using reference pyproject.toml and uv.lock, configures workspace rules, and ensures Agentic Ecology skills are discoverable. Use when initializing a new project workspace or bootstrapping a clean environment.
In this repository4 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Use this skill when you need to initialize a fresh, local project directory for ecological modeling workflows (such as bioacoustics or …
- Distinctive: line 22
Follow these sequential steps to set up the local workspace:
- Distinctive: line 27
Ensure the target project directory exists.
- Very specific: line 28
Run uv init --python 3.12 --no-readme && rm main.py in the project directory if it has not already been initialized.
- Distinctive: line 37
Create standard working subdirectories:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agentic Ecology Project Initialization Skill
Use this skill when you need to initialize a fresh, local project directory for
ecological modeling workflows (such as bioacoustics or camera trap analysis)
without cloning the entire agentic_ecology repository into the user's project
workspace.
Workflow Overview
Follow these sequential steps to set up the local workspace:
- Identify Target Working Directory:
- Confirm the root directory of the user's project workspace.
- Initialize Project & Scaffolding:
- Ensure the target project directory exists.
- Run
uv init --python 3.12 --no-readme && rm main.pyin the project directory if it has not already been initialized. This pins.python-versionto 3.12, generates.gitignore, initializes version control tracking, and removes the placeholder entrypoint. - Install the following skills locally with
npx skills add:google-deepmind/agentic_ecology(all skills).googlecolab/google-colab-cli(colab-operatorskill).googleworkspace/cli(gws-sharedandgws-drive-uploadskills).google/skills(gcloud,google-cloud-storage-basics,google-cloud-storage-bucket-architect,google-cloud-storage-fuse, andcloud-logging-query-generationskills).
- Create standard working subdirectories:
agent_workspace/: Sandboxed folder for agent scripts, server.databases/: Destination folder for Hoplite vector databases.data/: Destination folder for raw datasets (e.g., audio, images).
- Copy Reference Dependency Configurations:
- Overwrite the generated
pyproject.tomland copyuv.lockfrom this skill'sassets/directory into the target project root. - Adjust the package name in
pyproject.tomlto match the user's project name if desired, keeping all core dependencies (perch-hoplite,speciesnet), constraints, and build configurations intact.
- Overwrite the generated
- Install Workspace Rules (
AGENTS.md):- Copy the reference
AGENTS.mdfrom this skill'sassets/directory into the appropriate location in the project workspace to establish standard Agentic Ecology guidelines (compute assessment and offloading protocols, macOS dynamic library deadlock rules, Linux PyTorch/TensorFlow import order rules, SQL log suppression filters, and rules prohibiting Google copyright headers on generated workspace code).
- Copy the reference
- Synchronize Environment with
uv:- Execute
uv syncfrom the target project root to create the local virtual environment (.venv) and install all pinned dependencies.
- Execute
- Verify Environment Setup:
- Execute the verification script
scripts/verify_env.pyviauv run pythonto confirm that key libraries (perch_hoplite,speciesnet,soundfile,tensorflow) import cleanly.
- Execute the verification script
Technical Reference
For detailed command options, directory layout specifications, and verification code snippets, see:
- Initialization Technical Reference
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

