Install
$ agentstack add skill-etr-groundwork-setup-repo ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Setup Repository Skill
Configures the repository structure for Groundwork. Detects or asks whether this is a single-project repo or a monorepo, and creates .groundwork.yml for monorepos.
Workflow
Step 1: Detect Repository Structure
Look for common monorepo patterns:
- Multiple directories with their own
package.json,go.mod,Cargo.toml, etc. - Common monorepo directories:
apps/,packages/,services/,projects/ - Existing
specs/directory (suggests single-project) - Workspace configuration files (
pnpm-workspace.yaml,lerna.json,turbo.json)
Step 2: Ask User
Use AskUserQuestion to confirm:
> "I've analyzed your repo structure. Is this:" > - Single project — One project, specs at the repo root > - Monorepo — Multiple projects, each with their own specs
If monorepo indicators were found, mention them: > "I noticed [apps/, packages/, workspace config], which suggests a monorepo structure."
Step 3: Configure
If single project:
- No config file needed
- Ensure
.groundwork-plans/is in.gitignore(add it if missing) — work-on writes per-task plan files there. - Confirm: "Single-project mode. Specs will be stored in
specs/at the repo root." - Proceed — no
.groundwork.ymlcreated.
If monorepo:
- Ask which directories are projects. Suggest based on detected structure.
- Use
AskUserQuestionwith multi-select to confirm project list. - Create
.groundwork.yml:
version: 1
projects:
:
path:
:
path:
- Ensure
.groundwork.localand.groundwork-plans/are in.gitignore(add any missing entries)..groundwork-plans/is where work-on writes per-task plan files. - Ask which project to start with using
AskUserQuestion. - Set project context:
GROUNDWORK_PROJECT=andGROUNDWORK_PROJECT_ROOT=
Step 4: Persist Selection
For monorepo mode, persist the selection to .groundwork.local at the repo root (gitignored) so it survives session restarts.
Confirm: "Project **** selected. Specs will be stored in /specs/."
Adding Projects Later
This skill can also be invoked to add or remove projects from an existing .groundwork.yml:
- Read existing config
- Present current projects
- Ask what to add/remove
- Update the config file
Edge Cases
| Situation | Response | |-----------|----------| | .groundwork.yml already exists | Show current config, ask if user wants to modify | | No obvious project directories | Ask user to specify paths manually | | User says single-project but monorepo indicators exist | Accept user's choice, note the indicators |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: etr
- Source: etr/groundwork
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.