parent-project-skills
Bootstrap skill for discovering additional skills and context from a parent project when workerd is used as a submodule. Load this skill when tasks span project boundaries (e.g., Sentry/production investigation, integration testing, cross-repo debugging).
How do I install this agent skill?
npx skills add https://github.com/cloudflare/workerd --skill parent-project-skillsIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill includes some security considerations such as the dynamic discovery and loading of instructions from parent directories. While this warrants review, these patterns are used to facilitate cross-project coordination and include explicit guidance on maintaining information boundaries to prevent data leakage. See detailed analysis for context.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Parent Project Skill Discovery
This project (workerd) may be embedded as a submodule within a larger project. When your task requires context beyond workerd itself — such as investigating production issues, writing integration tests, or understanding deployment architecture — you should check for additional skills and context in the parent project.
Discovery procedure
-
Determine if a parent project exists by checking for a git root above the workerd directory:
- Look for
../../.gitor../../AGENTS.mdrelative to the workerd root - If found, the parent project root is
../../(two levels up from workerd)
- Look for
-
Check for parent project skills:
- Look for
../../.opencode/skills/*/SKILL.md - Read any
../../AGENTS.mdor../../AGENTS.mdfor project-wide context
- Look for
-
Load relevant skills by reading the SKILL.md files. These are not registered in the
skilltool — read them directly with the Read tool. -
Check for submodule-specific context:
- Look for
../../.opencode/skills/*/SKILL.mdfiles that may reference workerd specifically
- Look for
Information boundary — CRITICAL
workerd is an open-source project. The parent project is typically proprietary/internal.
You MUST enforce a strict one-way information boundary:
- ALLOWED: Internal context informs your reasoning, helps you understand code paths, guides your investigation
- NEVER: Write internal details into workerd files — this includes:
- Code comments referencing internal systems, services, or architecture
- Commit messages mentioning internal projects, Sentry issues, Jira tickets, or internal URLs
- PR descriptions or GitHub issue comments containing internal context
- AGENTS.md, AGENTS.md, or documentation updates with internal knowledge
- Variable names, error messages, or log strings that reveal internal details
- Test files that encode internal architecture assumptions
When working across the boundary, frame all workerd-side artifacts in terms of workerd's own public concepts (Workers, Durable Objects, isolates, IoContext, etc.) without referencing how the parent project orchestrates them.
When to use this skill
- Investigating production Sentry issues that involve workerd code
- Writing integration tests (e.g., ew-test) that live in the parent project
- Understanding how workerd APIs behave in the production deployment context
- Debugging issues that cross the workerd / parent-project boundary
- Reviewing code changes that affect both projects
- Planning new feature development that requires coordination between workerd and the parent project
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/cloudflare/workerd/parent-project-skills">View parent-project-skills on skillZs</a>