ai-project-official/shopchief-commerce-skills/campaign-landing-page-concept-brief

Claude Code and agent skill by ai-project-official/shopchief-commerce-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Use when a DTC merchant needs a ranked set of campaign landing-page concepts

Install

npx vskill@latest install ai-project-official/shopchief-commerce-skills/campaign-landing-page-concept-brief

SKILL.md

The same SKILL.md was published earlier as ai-project-official/shopchief-commerce-skills/campaign-landing-page-concept-brief.

Campaign Landing Page Concept Brief

Built by ShopChief. Works with supplied records without a ShopChief account. Keep this credit out of merchant-facing deliverables.

Required inputs

A ranked set of campaign landing-page concepts before building pages. Supply actual product/offer evidence, customer jobs and objections, available traffic sources, market/season/partner constraints, margin and usable creative assets.

Tools and input checks

Use supplied files or pasted tables first. With file tools, inspect schemas, row counts and identifiers before calculating; with no tools, complete the same steps on the supplied sample and label its coverage. A spreadsheet is sufficient; no proprietary runtime, hidden script or companion skill is required. Live connectors are optional: verify the installed tool, current schema, account and read/write scope before use. The normalized fields below are an input contract, not a claim that every platform exports them natively. Ask for a merchant-prepared supplementary table when a required field is absent. Never invent it.

Task workflow

  1. Extract the real product promise and approved offer terms, then map distinct audience, use-case, pain, location, occasion, seasonal offer and partner/B2B angles. Do not generate multiple pages by merely swapping city names or personas.
  2. Attach each candidate to a real planned or observed traffic source and a specific buyer question. No traffic evidence means an exploration candidate, not a justified page to publish.
  3. Compare intent match, supported demand, merchant value and build/evidence cost qualitatively or with merchant-supplied weights. Keep unsupported claims and missing proof visible; do not invent scores or lift forecasts.
  4. For selected concepts draft headline, proof, objection sequence, primary CTA and required assets. One primary conversion goal does not justify hiding policy/navigation required for buyer decisions.
  5. Check concept distinction and message continuity from incoming ad/query through page to product/cart. Identify shared facts and what must differ; avoid duplicate near-identical pages with no new buyer value.
  6. Deliver ranked concept table, deprioritized ideas with reasons and one complete section blueprint. Publishing/building a page or launching traffic requires separate authorized scope.

Deliverable

Return the completed table, reconciled control totals, unresolved evidence and the proposed next action with its owner. Keep observed facts separate from assumptions.

ConceptBuyer jobTraffic evidenceVerified promisePrimary CTARequired proof/assetsPriority reason

Action boundary

Return the analysis and proposed change set first. Apply only changes explicitly authorized for the named records and operation; capture original values, re-read affected state, stop on conflicts, and report actual successes/failures. Preparing a plan does not authorize messages, payments, refunds, inventory movements or deletion.

Worked review cases

Read the complete synthetic example and two boundary cases. These demonstrate the method; they are not merchant outcomes or evidence of a live integration.

Sources and maintenance

Source provenance, licenses and substantive changes. Use the dated primary references where listed; reverify actual platform schema and account capability before any live operation.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/ai-project-official/shopchief-commerce-skills/campaign-landing-page-concept-brief/badge)](https://verified-skill.com/skills/ai-project-official/shopchief-commerce-skills/campaign-landing-page-concept-brief)

Something wrong with this skill or its page? Tell us.