Repurpose content across channels. Use when: blog-to-social, webinar-to-article, pillar derivatives, format adaptation.
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill content-repurpose
Take one piece of existing content and generate a comprehensive repurposing plan across multiple channels and formats. Produces derivative content pieces, a posting schedule, and platform-specific adaptations to maximize the ROI of every content investment.
The user must provide (or will be prompted for):
~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply voice, compliance, industry context. Check guidelines/_manifest.json for restrictions, messaging, channel styles, voice-and-tone rules, and templates. If a template matching this command exists in ~/.claude-marketing/brands/{slug}/templates/, apply its format. If no brand exists, prompt for /digital-marketing-pro:brand-setup or proceed with defaults.python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns to identify related campaigns and previously published content that derivative pieces can reference or link to.skills/context-engine/platform-specs.md for character limits, image dimensions, video lengths, hashtag best practices, and format requirements per platform. Adapt each piece to fit native platform conventions.channel-styles.md, apply platform-specific tone adjustments (e.g., more casual on social, more authoritative in email, more concise on Twitter/X).10. Add tracking and attribution: Attach UTM parameters to all links in derivative content so traffic driven back to the original or landing pages can be attributed to the specific repurposed piece and platform.
11. Define performance metrics per format: Set engagement benchmarks for each derivative piece (impressions, clicks, shares, saves, comments) based on platform averages and brand historical performance.
A structured content repurposing plan containing:
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take indranilbanerjee/content-repurpose from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.