Initial commit
This commit is contained in:
31
skills/asset-approval/SKILL.md
Normal file
31
skills/asset-approval/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: asset-approval
|
||||
description: Use to manage co-marketing asset reviews with traceable evidence and
|
||||
SLAs.
|
||||
---
|
||||
|
||||
# Asset Approval Workflow Skill
|
||||
|
||||
## When to Use
|
||||
- Coordinating creative reviews across multiple partner stakeholders.
|
||||
- Auditing compliance for regulated industries.
|
||||
- Preventing go-live delays caused by unclear feedback loops.
|
||||
|
||||
## Framework
|
||||
1. **Review Matrix** – define reviewers per asset type (brand, legal, product, regional) and required evidence.
|
||||
2. **SLA Cadence** – set response times, reminder schedule, and escalation triggers.
|
||||
3. **Feedback Channels** – standardize annotation tools, version naming, and acceptance criteria.
|
||||
4. **Sign-off Logging** – capture final approvals with timestamps, approver names, and file hashes.
|
||||
5. **Change Control** – document post-approval edits, expiration dates, and refresh plans.
|
||||
|
||||
## Templates
|
||||
- Approval tracker (asset → reviewer → status → notes → evidence link).
|
||||
- SLA chart outlining response times by priority level.
|
||||
- Change request form for post-approval edits.
|
||||
|
||||
## Tips
|
||||
- Use shared storage with permissions per partner to prevent accidental edits.
|
||||
- Pair with `co-branding` skill to auto-check brand compliance before review.
|
||||
- Automate reminders via project tools to keep cross-company teams on schedule.
|
||||
|
||||
---
|
||||
31
skills/attribution/SKILL.md
Normal file
31
skills/attribution/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: attribution
|
||||
description: Use to define measurement, data sharing, and ROI reporting for joint
|
||||
campaigns.
|
||||
---
|
||||
|
||||
# Co-marketing Attribution Playbook Skill
|
||||
|
||||
## When to Use
|
||||
- Planning measurement strategy for joint campaigns or events.
|
||||
- Reconciling attribution discrepancies between partner analytics stacks.
|
||||
- Preparing executive or partner reports on shared pipeline/revenue impact.
|
||||
|
||||
## Framework
|
||||
1. **Taxonomy Alignment** – agree on UTM structure, campaign IDs, stages, and conversion definitions.
|
||||
2. **Data Exchange** – determine cadence, format, security requirements, and normalization rules.
|
||||
3. **Attribution Models** – select methods (first/last/multi-touch, split attribution, weighted models) and document assumptions.
|
||||
4. **Governance** – define owners for metric updates, dispute resolution, and audit trails.
|
||||
5. **Storytelling** – package dashboards and narratives for stakeholders, highlighting joint impact and next steps.
|
||||
|
||||
## Templates
|
||||
- Attribution worksheet (source → partner → funnel stage → revenue).
|
||||
- Data sharing checklist (fields, format, frequency, security).
|
||||
- Reporting deck outline (KPIs, insights, actions).
|
||||
|
||||
## Tips
|
||||
- Run attribution dry-runs before launch to catch data gaps.
|
||||
- Include qualitative context (partner reach, brand lift) alongside quantitative metrics.
|
||||
- Pair with `track-source` command to keep reports consistent across cycles.
|
||||
|
||||
---
|
||||
31
skills/co-branding/SKILL.md
Normal file
31
skills/co-branding/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: co-branding
|
||||
description: Use to enforce visual, messaging, and legal standards across partner
|
||||
campaigns.
|
||||
---
|
||||
|
||||
# Co-branding Guidelines Skill
|
||||
|
||||
## When to Use
|
||||
- Designing shared assets, landing pages, and creative for partner initiatives.
|
||||
- Reviewing partner-submitted collateral before distribution.
|
||||
- Training agencies or external teams on brand usage.
|
||||
|
||||
## Framework
|
||||
1. **Brand Hierarchy** – determine logo lockups, dominance rules, color usage, and typography.
|
||||
2. **Messaging Alignment** – define shared narrative, value props, boilerplate, and CTA guidance.
|
||||
3. **Legal/Compliance** – include disclaimers, TM/® usage, privacy statements, and required approvals.
|
||||
4. **Localization** – document translation rules, regional references, and regulatory considerations.
|
||||
5. **Version Control** – track asset versions, expiry dates, and update cadence.
|
||||
|
||||
## Templates
|
||||
- Co-branding checklist (logos, copy, disclaimers, accessibility, localization).
|
||||
- Messaging matrix (audience → key message → proof points → CTA).
|
||||
- Visual reference guide with approved mockups.
|
||||
|
||||
## Tips
|
||||
- Keep editable templates in shared workspaces to reduce iteration time.
|
||||
- Pair with `asset-approval` skill for evidence tracking.
|
||||
- Log exceptions with rationale and expiration date.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user