Agent onboarding

Install the DASCore skills and browse the included workflows.

DASCore provides several tools to help coding agents use it more effectively. Start by installing the skills and have your agent explore the API.

Install the skills

With library-skills

DASCore ships its skills in dascore/.agents/skills/, the layout library-skills reads. From a project whose environment has DASCore installed, run:

uvx library-skills

It finds the skills of the project’s dependencies and asks which to link into .agents/skills. Claude Code reads only .claude/skills, so add --claude for it.

Or just ask your agent:

Run uvx library-skills --claude --all -y to install the DASCore skills into this project.

Included skills

dascore is the entry point: it finds the APIs and workflows of the DASCore installed in your project.

Skill	Documentation	Purpose
dascore	Choose a DASCore workflow	Use the installed DASCore APIs and workflow recipes when analyzing distributed fiber-optic sensing data or writing Python code that uses DASCore.
dascore-make-annotations	Make a DASCore annotation set	Build a DASCore annotation set from a table of picks, ranges, paths, or polygons, then query, plot, and save it.
dascore-make-inventory	Create an inventory	Create, validate, repair, serialize, and attach a DASCore inventory of a fiber deployment, following a worked tunnel example.
dascore-make-namespace	Extending DASCore	Add methods to DASCore’s Patch, Spool, Inventory, or AnnotationSet from a local namespace or a plugin package, and define patch processors and backend kernels.
dascore-migrate-to-v1	Migrate to DASCore 1.0	Update code, files, and indexes written for DASCore 0.1.x to the DASCore 1.0 APIs, including behavior that changed without raising.
dascore-test-beta	Test the latest DASCore pre-release	Try the newest DASCore pre-release on an existing project’s code and data in an isolated environment, compare it with the project’s current version, and draft reports of what breaks.

Run dascore skills to list available workflows, or dascore skill <name> to read one. Each link is the same procedure served by the CLI. The annotation and beta-testing skills are written for agents and have no docs page, so their links go to the skill files; the annotations tutorial covers the same tools for people. The migration and beta-testing skill files can also be given directly to an agent without installing the skill.

Development skills

These are for work on DASCore itself; their descriptions begin with “DASCore development”.

Skill	Documentation	Purpose
dascore-add-format	Adding a New Format	Add a file format with a FiberIO subclass, covering metadata, array windows, attrs, tests, and entry-point registration.
dascore-draft-release	Draft a release	Draft the next release by proposing the next v* tag and a categorized changelog from the PRs merged into the release branch (usually dev) since the last release.
dascore-start-task	Start a task	Set up an isolated task worktree and environment when starting work on DASCore itself.

Where skills live

Every skill is a SKILL.md file under dascore/.agents/skills/ in the installed package, where tools that link skills from a project’s dependencies find them.