feat(creative-strategy-foundations): baseline creative-strategy skills package

[rezakhadjavi]

Summary

Adds the creative-strategy-foundations v1 package as one component of the configured Runneth baseline.

• Installs three foundational creative-strategy skills into package-namespaced Brain paths:
  • /agent/brain/skills/creative-strategy-foundations/analyzing/SKILL.md
  • /agent/brain/skills/creative-strategy-foundations/briefing/SKILL.md
  • /agent/brain/skills/creative-strategy-foundations/creative-generation/SKILL.md
• Uses recursive skill discovery available on staging, so the nested <package>/<skill>/SKILL.md layout remains discoverable while avoiding collisions with skills owned by other packages.
• Adds core-creative-skills as a package_instruction. It is intentionally not a fourth Brain skill or visible Brain directory:
  • the package manager stages it at /agent/.runneth/packages/instructions/creative-strategy-foundations/core-creative-skills.md
  • the runtime loads it into future system prompts as creative-strategy-foundations/core-creative-skills
  • its content identifies the three installed skills and points the agent to their namespaced SKILL.md paths
• Registers the package in package-index.json with categories: ["baseline"], installPolicy: auto, updatePolicy: auto, and uninstallPolicy: protected.
• Keeps source.ref set to main per the package-index validator contract (fix(packages): align package index validation contracts #184); staging serving is handled by the staging builder, not the ref field.

Why

default and baseline describe package-selection policy, not ownership by a single package. The baseline can contain multiple focused packages. Naming this package creative-strategy-foundations limits its ownership to the foundational analyze, generate, and brief workflows while allowing other baseline capabilities to remain independently packaged.

The package namespace also makes resource ownership explicit and prevents these generic skill names from colliding with resources installed by other packages. Its protected uninstall policy keeps this baseline capability from being removed through the normal package uninstall flow.

Validation

• node --test scripts/validate-runneth-package-index.mjs — 11/11 tests pass locally.
• Simulated the pull-request validation environment with runneth-fleet-change-approved present — 11/11 tests pass.
• Packaged analyzing, briefing, and creative-generation skills match Agent Builder staging at 4b097158f byte-for-byte.
• The package manifest and index versions match at 1.
• The package is protected from uninstall through uninstallPolicy: protected in both the manifest and index.
• The site build and security behavior job passed on the prior revision; GitHub Actions will rerun against this pushed commit.

Notes

• core-creative-skills will not appear in the Brain sidebar because it is prompt context, not a skill resource.
• Conversations whose system prompt was assembled before installation need a fresh runtime/conversation to receive the package instruction and refreshed skill discovery.
• Anyone who explicitly installed the earlier unmerged runneth-default test package should uninstall it before installing creative-strategy-foundations; changing the package ID creates a new package identity rather than an in-place upgrade.
• Because this is a new managed-sync package, the PR-only fleet gate requires the runneth-fleet-change-approved label after core engineering review.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[greptile-apps]

Confidence Score: 5/5

The manifest, index entry, and validator contract are fully aligned; all policy fields, key sets, and source coordinates match their expected values.

The package adds entirely new files with no modifications to existing logic. The manifest and index entry are consistent on every compared field, and all resource types and paths satisfy the validator assertions. The fleet approval label requirement was already surfaced in a prior review comment and is acknowledged in the PR description.

Files Needing Attention: No files require special attention. The fleet-approval label gate in CI is noted but was covered in a prior review comment.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Package Manager installs\ncreative-strategy-foundations] --> B[Copies skill directories\nto agent_brain/skills/\ncreative-strategy-foundations/]
    A --> C[Stages package_instruction\ncore-creative-skills.md]

    B --> D[analyzing/SKILL.md]
    B --> E[briefing/SKILL.md]
    B --> F[creative-generation/SKILL.md]

    C --> G[Runtime loads instruction\ninto system prompt as\ncreative-strategy-foundations/core-creative-skills]

    G --> H{Agent receives task}
    H -->|Analysis task| D
    H -->|Brief task| E
    H -->|Generation task| F

    D --> I[Executes motion CLI,\nreference reads, analysis output]
    E --> J[Builds brief from concept,\nperformance data, or script]
    F --> K[Generates hooks, concepts,\nmessaging angles, audience strategy]

Loading

_{Reviews (8): Last reviewed commit: "Merge branch 'staging' into vamsi/runnet..." | Re-trigger Greptile}