Skip to content

Add next-create-campaign skill and update campaign documentation - #56

Merged
brettstirlingbond merged 1 commit into
mainfrom
claude/update-skills-docs-page-b5ifpt
Sep 14, 2026
Merged

brettstirlingbond merged 1 commit into
mainfrom
claude/update-skills-docs-page-b5ifpt

Conversation

@brettstirlingbond

Copy link
Copy Markdown
Contributor

Summary

This PR introduces a new AI agent skill for provisioning campaigns via the Admin API and clarifies the relationship between campaign creation and setup workflows.

Key Changes

  • New skill added: next-create-campaign — provisions launch-ready Campaigns App campaigns over the Admin API, handling catalogue/gateway/shipping method discovery, campaign structure recommendations, and creation of campaigns, packages, shipping methods, and tier/voucher offers
  • Updated skill descriptions: Clarified that next-campaigns-setup now operates on campaigns that already exist in the Campaigns App (post-provisioning workflow)
  • Capability documentation:
    • Added next-create-campaign to the campaigns capability skills list
    • Added next-create-campaign to the AI agent skills capability
    • Updated AI agent skills summary to reference "campaign provisioning and setup" instead of just "campaign setup"
  • Verification dates: Updated last_verified timestamps from 2026-09-03 to 2026-09-14 for affected capabilities

Implementation Details

The changes establish a clear two-step campaign workflow:

  1. Provision (next-create-campaign): Creates the campaign infrastructure in the Campaigns App via Admin API
  2. Setup (next-campaigns-setup): Configures the local project, seeds configuration files, and wires up API credentials and analytics

This separation allows agents to handle campaign creation independently before developers begin funnel work.

https://claude.ai/code/session_012Q12RTvLPkvmxxZEBMjKfY

next-create-campaign (v0.3.0) shipped in NextCommerceCo/skills but was
missing from the docs, so there was no way to discover it.

- Add the table row, placed above next-campaigns-setup since it is the
  upstream half of the pair: it provisions the campaign over the Admin
  API and hands back the api_key and package ids that the CPK scaffold
  then consumes.
- Clarify next-campaigns-setup's "when to use it" cell so the two
  campaigns skills don't read as alternatives.
- Register the skill in the campaigns and agent-skills capability
  records so /capabilities.json and the llms bundles list it, and bump
  their last_verified.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Q12RTvLPkvmxxZEBMjKfY
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
developer-docs 040be47 Commit Preview URL

Branch Preview URL
Sep 14 2026, 12:22 AM

@kilo-code-bot

kilo-code-bot Bot commented Sep 14, 2026

Copy link
Copy Markdown

Code Review Summary

Status: No Issues Found | Recommendation: Merge

The PR cleanly adds the new next-create-campaign skill to both the AI Skills page table and the campaigns and agent-skills capability records in content/capabilities.yaml. The two affected last_verified timestamps are bumped consistently to 2026-09-14, the new skill is correctly placed upstream of next-campaigns-setup (matching the provisioning-then-setup narrative), and the next-campaigns-setup "when to use it" cell is updated to make the two skills read as a sequence rather than alternatives. The summary text on the agent-skills capability (campaign provisioning and setup) is consistent with the new entry. No bugs, factual drift, or ordering issues found in the changed lines.

Files Reviewed (2 files)
  • content/capabilities.yaml
  • content/docs/skills/index.mdx

Reviewed by minimax-m3 · Input: 0 · Output: 0 · Cached: 0

@brettstirlingbond
brettstirlingbond merged commit a6ed365 into main Sep 14, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants