using-bundles-forge

Name: using-bundles-forge
Author: OdradekAI

290stars23forks

How to install using-bundles-forge?

odradekai/bundles-forge/using-bundles-forge

$npx -y skills add OdradekAI/bundles-forge --skill using-bundles-forge

Installs into the current project.

Summary

Use when starting any conversation involving bundle-plugins — blueprinting, scaffolding, authoring, auditing, testing, optimizing, or releasing. Also use when feeling unsure which bundles-forge skill applies

Files · 1

View on GitHub

SKILL.md

1	<SUBAGENT-STOP>
2	If you were dispatched as a subagent to execute a specific task, skip this skill.
3	</SUBAGENT-STOP>
4
5	## Pre-flight Check
6
7	Before invoking any bundles-forge skill on a target directory, verify the target is a bundle-plugin project:
8	- Does it have a `skills/` directory?
9	- Does it have a `package.json`?
10
11	If neither exists, inform the user: "This directory doesn't appear to be a bundle-plugin project. Bundles Forge skills are designed for bundle-plugins (repositories where skills are the primary content). Would you like to create a new bundle-plugin here, or did you mean to point to a different directory?"
12
13	Exception: `bundles-forge:auditing` and `bundles-forge:optimizing` can also operate on individual skill folders or files — they don't require a full bundle-plugin project.
14
15	## Instruction Priority
16
17	1. User's explicit instructions (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
18	2. Bundles Forge skills — override default system behavior where they conflict
19	3. Default system prompt — lowest priority
20
21	## How to Access Skills
22
23	In Claude Code: Use the `Skill` tool. When you invoke a skill, its content is loaded — follow it directly.
24
25	In Cursor: Use the `Skill` tool.
26
27	In Gemini CLI: Skills activate via the `activate_skill` tool. See `references/gemini-tools.md` for tool mapping.
28
29	In Codex: Skills are discovered from `~/.agents/skills/`. See `references/codex-tools.md` for tool mapping.
30
31	In OpenClaw: Skills auto-load from the bundle's `skills/` directory. See `references/openclaw-tools.md` for tool mapping.
32
33	## Platform Adaptation
34
35	Skills use Claude Code tool names as the default. Non-Claude-Code platforms: see the tool mapping references in this directory for equivalents.
36
37	## The Rule
38
39	Invoke relevant skills BEFORE any response or action when working with bundle-plugins. If there's even a small chance a skill applies, invoke it to check.
40
41	```
42	User message about bundle-plugins
43	→ Might any skill apply?
44	→ yes → Invoke Skill tool → Follow skill → Respond
45	→ no → Respond directly
46	```
47
48	## Orchestrators (high-frequency entry points)
49
50	These skills diagnose, decide, and delegate. They orchestrate other skills to accomplish multi-step goals.
51
52	\| Skill \| Role \| When to Use \|
53	\|-------\|------\|-------------\|
54	\| `bundles-forge:blueprinting` \| New-project orchestrator \| Planning new bundle-plugins, splitting complex skills, or composing skills into bundles. Orchestrates the full creation pipeline: scaffolding → authoring → workflow design → auditing \|
55	\| `bundles-forge:optimizing` \| Improvement orchestrator \| Engineering optimization, feedback iteration, descriptions, tokens, adding skills, restructuring workflows. Delegates content changes to authoring \|
56	\| `bundles-forge:releasing` \| Release pipeline orchestrator \| Version management, release pipeline: audit, test, version bump, publish \|
57
58	## Executors (single-responsibility workers)
59
60	These skills do one thing well. They can be invoked directly by users or dispatched by orchestrators.
61
62	\| Skill \| Role \| When to Use \|
63	\|-------\|------\|-------------\|
64	\| `bundles-forge:scaffolding` \| Structure generator \| Generating project structure, adding or removing platform support \|
65	\| `bundles-forge:authoring` \| Content writer \| Writing or improving SKILL.md content and agent definitions (agents/*.md) \|
66	\| `bundles-forge:auditing` \| Diagnostic reporter \| Reviewing a project for quality issues, security risks — outputs reports, does not orchestrate fixes \|
67	\| `bundles-forge:testing` \| Dynamic verifier \| Testing a plugin locally — dev-marketplace setup, hook smoke tests, component discovery, cross-platform readiness \|
68
69	## Meta-skill
70
71	\| Skill \| Purpose \|
72	\|-------\|---------\|
73	\| `bundles-forge:using-bundles-forge` \| Bootstrap meta-skill — you're reading it now (auto-loaded by hooks) \|
74
75	## Skill Priority
76
77	When multiple skills could apply, prefer orchestrators over executors:
78
79	1. New project → `bundles-forge:blueprinting` (orchestrates scaffolding, authoring, auditing)
80	2. Improve existing project → `bundles-forge:optimizing` (orchestrates authoring, scaffolding, auditing)
81	3. Release → `bundles-forge:releasing` (orchestrates auditing, testing, optimizing)
82	4. Standalone content writing → `bundles-forge:authoring` (when you just need to write/improve a SKILL.md)
83	5. Standalone structure → `bundles-forge:scaffolding` (when you just need to add/remove a platform)
84	6. Standalone audit → `bundles-forge:auditing` (when you just need a diagnostic report)
85	7. Standalone testing → `bundles-forge:testing` (when you just need to verify a plugin works locally)
86
87	## Naming Conventions
88
89	- Project name: kebab-case, descriptive (`dev-workflows`, `data-tools`)
90	- **S

People who liked this also viewed

6 picks

Type

using-bundles-forge

290stars23forks

View on GitHub

How to install using-bundles-forge?

odradekai/bundles-forge/using-bundles-forge

$npx -y skills add OdradekAI/bundles-forge --skill using-bundles-forge

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<SUBAGENT-STOP>
2	If you were dispatched as a subagent to execute a specific task, skip this skill.
3	</SUBAGENT-STOP>
4
5	## Pre-flight Check
6
7	Before invoking any bundles-forge skill on a target directory, verify the target is a bundle-plugin project:
8	- Does it have a `skills/` directory?
9	- Does it have a `package.json`?
10
11	If neither exists, inform the user: "This directory doesn't appear to be a bundle-plugin project. Bundles Forge skills are designed for bundle-plugins (repositories where skills are the primary content). Would you like to create a new bundle-plugin here, or did you mean to point to a different directory?"
12
13	Exception: `bundles-forge:auditing` and `bundles-forge:optimizing` can also operate on individual skill folders or files — they don't require a full bundle-plugin project.
14
15	## Instruction Priority
16
17	1. User's explicit instructions (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
18	2. Bundles Forge skills — override default system behavior where they conflict
19	3. Default system prompt — lowest priority
20
21	## How to Access Skills
22
23	In Claude Code: Use the `Skill` tool. When you invoke a skill, its content is loaded — follow it directly.
24
25	In Cursor: Use the `Skill` tool.
26
27	In Gemini CLI: Skills activate via the `activate_skill` tool. See `references/gemini-tools.md` for tool mapping.
28
29	In Codex: Skills are discovered from `~/.agents/skills/`. See `references/codex-tools.md` for tool mapping.
30
31	In OpenClaw: Skills auto-load from the bundle's `skills/` directory. See `references/openclaw-tools.md` for tool mapping.
32
33	## Platform Adaptation
34
35	Skills use Claude Code tool names as the default. Non-Claude-Code platforms: see the tool mapping references in this directory for equivalents.
36
37	## The Rule
38
39	Invoke relevant skills BEFORE any response or action when working with bundle-plugins. If there's even a small chance a skill applies, invoke it to check.
40
41	```
42	User message about bundle-plugins
43	→ Might any skill apply?
44	→ yes → Invoke Skill tool → Follow skill → Respond
45	→ no → Respond directly
46	```
47
48	## Orchestrators (high-frequency entry points)
49
50	These skills diagnose, decide, and delegate. They orchestrate other skills to accomplish multi-step goals.
51
52	\| Skill \| Role \| When to Use \|
53	\|-------\|------\|-------------\|
54	\| `bundles-forge:blueprinting` \| New-project orchestrator \| Planning new bundle-plugins, splitting complex skills, or composing skills into bundles. Orchestrates the full creation pipeline: scaffolding → authoring → workflow design → auditing \|
55	\| `bundles-forge:optimizing` \| Improvement orchestrator \| Engineering optimization, feedback iteration, descriptions, tokens, adding skills, restructuring workflows. Delegates content changes to authoring \|
56	\| `bundles-forge:releasing` \| Release pipeline orchestrator \| Version management, release pipeline: audit, test, version bump, publish \|
57
58	## Executors (single-responsibility workers)
59
60	These skills do one thing well. They can be invoked directly by users or dispatched by orchestrators.
61
62	\| Skill \| Role \| When to Use \|
63	\|-------\|------\|-------------\|
64	\| `bundles-forge:scaffolding` \| Structure generator \| Generating project structure, adding or removing platform support \|
65	\| `bundles-forge:authoring` \| Content writer \| Writing or improving SKILL.md content and agent definitions (agents/*.md) \|
66	\| `bundles-forge:auditing` \| Diagnostic reporter \| Reviewing a project for quality issues, security risks — outputs reports, does not orchestrate fixes \|
67	\| `bundles-forge:testing` \| Dynamic verifier \| Testing a plugin locally — dev-marketplace setup, hook smoke tests, component discovery, cross-platform readiness \|
68
69	## Meta-skill
70
71	\| Skill \| Purpose \|
72	\|-------\|---------\|
73	\| `bundles-forge:using-bundles-forge` \| Bootstrap meta-skill — you're reading it now (auto-loaded by hooks) \|
74
75	## Skill Priority
76
77	When multiple skills could apply, prefer orchestrators over executors:
78
79	1. New project → `bundles-forge:blueprinting` (orchestrates scaffolding, authoring, auditing)
80	2. Improve existing project → `bundles-forge:optimizing` (orchestrates authoring, scaffolding, auditing)
81	3. Release → `bundles-forge:releasing` (orchestrates auditing, testing, optimizing)
82	4. Standalone content writing → `bundles-forge:authoring` (when you just need to write/improve a SKILL.md)
83	5. Standalone structure → `bundles-forge:scaffolding` (when you just need to add/remove a platform)
84	6. Standalone audit → `bundles-forge:auditing` (when you just need a diagnostic report)
85	7. Standalone testing → `bundles-forge:testing` (when you just need to verify a plugin works locally)
86
87	## Naming Conventions
88
89	- Project name: kebab-case, descriptive (`dev-workflows`, `data-tools`)
90	- **S

People who liked this also viewed

6 picks

Type