# Getting Started
This guide shows how to add Bake Agent Context tasks to a Rust project and install context from its Cargo dependencies.
## Add the Bake tasks
Bake tasks belong in your project's private `bake/` crate. Bootstrap the task package, add Bake Agent Context, and regenerate the task links:
```sh
cargo install socketry-cargo-bake --locked
cargo bake --regenerate
cargo add --manifest-path bake/Cargo.toml bake-agent-context
cargo bake --regenerate
```
Regeneration links the dependency's task registrations while preserving your task source; no manual import is needed.
## Install dependency context
Run this from the project root:
```sh
cargo bake agent:context:install
```
The task scans resolved Cargo dependencies for a top-level `context/` directory, copies ordinary context files into `.agents/context/SELECTOR/`, and installs skill-marked documents and their resources into `.agents/skills/`. Discover installed guidance by listing Markdown files under the provider's context directory and reading the guides relevant to the task.
Use `cargo bake agent:context:list` to see which dependencies provide context. List one provider's definitions with `cargo bake agent:context:list --package CRATE`; skill documents are marked `(skill)`. Inspect a guide or skill with `cargo bake agent:context:show --package CRATE --file FILE`. The main install task installs ordinary context and all skills from the selected providers. The skill name uses the authored `name`, or defaults to `<crate>-<filename>`.
## Generated files
The install task maintains a marked block in the repository's local Git exclude file (`.git/info/exclude`) for installed context and dependency skills. Project-owned skill directories remain trackable. Repository instructions can direct agents to read relevant Markdown files under `.agents/context/`.
Installed `SKILL.md` front matter records `metadata.type: skill` and the resolved `metadata.ecosystem`, `metadata.package`, and `metadata.version`. Cargo refreshes reconcile skills within their selected ecosystem and package scope. A full refresh also removes skills from removed or empty providers. After resolving an installation error, rerun the command to refresh generated files.