channel-integration

31 stars 7 forks

Use when synchronizing messaging, timing, and measurement across multiple campaign channels.

Marketplace

Also in: networking

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →

Claude Code (CLI) Fast

skilz install gtmagents/gtm-agents/channel-integration

OpenCode (CLI) Fast

skilz install gtmagents/gtm-agents/channel-integration --agent opencode

OpenAI Codex (CLI) Native

skilz install gtmagents/gtm-agents/channel-integration --agent codex

Gemini CLI (Project) Project

skilz install gtmagents/gtm-agents/channel-integration --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents

For Claude Desktop Easy

Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

Manual Installation

1. Clone the repository:

git clone https://github.com/gtmagents/gtm-agents

2. Copy the agent skill directory:

cp -r gtm-agents/plugins/campaign-orchestration/skills/channel-integration ~/.claude/skills/

Owner: gtmagents (GitHub)
Repository: gtm-agents
Stars: 31
Forks: 7
Type: Technical
Meta-Domain: development
Primary Domain: testing
Market Score: 28

Agentic Skill Grades →

Agent Skill Grade

Score: 67/100 Click to see breakdown

Score Breakdown

Spec Compliance

12/15

PDA Architecture

18/30

Ease of Use

15/25

Writing Style

8/10

Utility

13/20

Modifiers: +1

Areas to Improve

Missing Template Implementations
No Reference Layer
Vague Trigger Description

Recommendations

Address 1 high-severity issues first
Add trigger phrases to description for discoverability
Add table of contents for files over 100 lines

Graded: 2026-01-24

Developer Feedback

I've been digging through skills lately and noticed your channel-integration approach—the way you're structuring cross-platform messaging could unlock some interesting scalability patterns, though I'm curious about some of the architectural decisions that brought the score down to 67. Worth a deeper look at the modularization and docs clarity.

Links:

The TL;DR

You're at 67/100, firmly in D territory—needs work before production. This is based on Anthropic's best practices for skill structure and utility. Your strongest area is Spec Compliance (12/15) with solid YAML and naming conventions, but Progressive Disclosure Architecture (18/30) and Ease of Use (15/25) are dragging things down—mostly because the frameworks are high-level concepts without the actual supporting materials that make them useful.

What's Working Well

Spec compliance is tight. Your YAML frontmatter is valid, naming follows kebab-case correctly, and you've got the basics locked down.
Consistent terminology throughout—you're using "channel," "campaign," and "messaging" in a coherent way without conflicting language.
Real problem being solved. Multi-channel coordination is a legitimate pain point, and your 6-step framework tackles something people actually need.

The Big One: Missing Template Implementations

This is the heaviest hitter. Your Templates section lists them by name only—"Channel calendar template," "UTM builder/validation sheet"—but provides zero actual implementations. That's like handing someone a recipe book with just chapter titles and no recipes.

Why it matters: Templates are supposed to be your reference layer. Without them, developers have to invent thei...

Browse Category

More development Agentic Skills

Report Security Issue

Found a security vulnerability in this agent skill?