Parent Project Skills
- 39 installs
- 8.5k repo stars
- Updated August 5, 2026
- cloudflare/workerd
parent-project-skills discovers parent skills when workerd is a submodule.
About
The parent-project-skills skill bootstraps discovery of additional skills when workerd is embedded in a larger proprietary parent project. Check ../../.git or ../../AGENTS.md for a parent root, then read ../../.opencode/skills/*/SKILL.md for relevant guidance. Enforce a strict one-way boundary: internal context may inform reasoning but must never appear in workerd commits, comments, PR text, tests, or docs. Use for production Sentry investigations, parent integration tests, cross-repo debugging, and deployment-context API behavior without leaking internal details into open-source workerd artifacts.
- Discovers parent project skills two levels above workerd root.
- Reads AGENTS.md and opencode skills directly.
- Enforces no internal details in workerd-side artifacts.
- For cross-repo debugging and integration testing.
- Frames workerd changes using public workerd concepts only.
Parent Project Skills by the numbers
- 39 all-time installs (skills.sh)
- Ranked #8,302 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
parent-project-skills capabilities & compatibility
- Capabilities
- parent skill discovery procedure and boundary ru
- Use cases
- orchestration
What parent-project-skills says it does
workerd is an open-source project. The parent project is typically proprietary/internal.
npx skills add https://github.com/cloudflare/workerd --skill parent-project-skillsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 39 |
|---|---|
| repo stars | ★ 8.5k |
| Last updated | August 5, 2026 |
| Repository | cloudflare/workerd ↗ |
How do I use internal context without leaking it into workerd commits?
Discover parent-project skills and enforce information boundaries when workerd is a submodule.
Who is it for?
workerd contributors working inside proprietary parent repos.
Skip if: Skip when workerd is standalone without a parent project.
When should I use this skill?
Task spans workerd and parent project boundaries.
What you get
Loaded parent skills with information boundary enforced on workerd edits.
Files
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
1. 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)
2. Check for parent project skills:
- Look for
../../.opencode/skills/*/SKILL.md - Read any
../../AGENTS.mdor../../AGENTS.mdfor project-wide context
3. Load relevant skills by reading the SKILL.md files. These are not registered in the skill tool — read them directly with the Read tool.
4. Check for submodule-specific context:
- Look for
../../.opencode/skills/*/SKILL.mdfiles that may reference workerd specifically
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
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10FAQ
What does parent-project-skills do?
parent-project-skills discovers parent skills when workerd is a submodule.
When should I use parent-project-skills?
Task spans workerd and parent project boundaries.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.