القائمة
Use when creating or validating referential plugin manifests, marketplace entries, primitive references, or payload-to-reference plugin conversions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Design OpenAPI component schemas with discriminated variants, constrained primitives, subtype/composition choices, nullability, examples, and invalid-state prevention.
Set up a repository for marketplace-driven AI tooling. Use when onboarding a new repo, refreshing a checked-in marketplace reference, installing core marketplace plugins, or documenting which configured marketplaces should be available by default.
Use when validation, authorization, normalization, or state checks produce facts later code must retain. Replace primitive contracts, flags, sentinel states, string protocols, and call-order conventions with proof-carrying values in any language.
Use when Kotlin work needs type-driven modeling, parse-dont-validate boundaries, semantic package layout, explicit failures, API review, or package cohesion checks.
Pkl engineering for typed configuration contracts, expressions, amendments, evaluation, formatting, tests, projects, dependencies, rendering, and packages. Use when a repository contains `.pkl` modules or `PklProject`, or when configuration behavior should be modeled and enforced with Apple Pkl.
Use when a behavior, invariant, bug fix, contract, or refactor should be developed red-green-refactor and any shell-invokable check can provide focused executable proof.
استنادا إلى تصنيف SOC المهني
| name | plugin-composition-authoring |
| description | Use when creating or validating referential plugin manifests, marketplace entries, primitive references, or payload-to-reference plugin conversions. |
Use this skill to create plugin manifests that assemble primitives already owned elsewhere in the repo. The plugin is the installable composition surface; the primitive remains usable without the plugin.
skills/*, agents/*, hooks/*,
and concepts/* inside the repository source/ graph.Define the plugin family. Name the composed capability set, the primitives it should assemble, and what should remain outside the plugin.
Confirm primitive independence. Verify every skill, agent, hook, and concept exists under the canonical root and makes sense without the plugin.
Write source/plugins/<name>/plugin.json.
Use local references to existing primitives. Keep metadata limited to
composition, version, and description.
Update source/adaptable.marketplace.json.
Add or update one plugin entry and any newly promoted primitive entries.
Preserve existing ordering unless a new order is part of the request.
Validate. Run the source graph gate and, for focused plugin review, the composition checker:
node source/tools/validate-source-graph.mjs
python3 source/skills/plugin-composition-authoring/scripts/check_plugin_composition --plugin <name>
source/adaptable.marketplace.json or plugin catalog metadata.source/adaptable.marketplace.json and plugin manifest references validate.