Instagram Marketing
sergebulaev/instagram-skills
Plan, draft, audit, and publish content for Instagram. An agent skill from sergebulaev/instagram-skills.
A skill your agent uses to enforce cadence rules, timezone coverage, and operational controls on social calendars.
Install Calendar Governance
$ npx skills add gtmagents/gtm-agents --skill calendar-governance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gtmagents/gtm-agents calendar-governance --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/social-scheduler-orchestration/skills/calendar-governance .claude/skills/calendar-governance && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "calendar-governance" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/social-scheduler-orchestration/skills/calendar-governance into .claude/skills/calendar-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-governance", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gtmagents/gtm-agents/tree/main/plugins/social-scheduler-orchestration/skills/calendar-governanceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gtmagents/gtm-agents --skill calendar-governance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gtmagents/gtm-agents calendar-governance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/social-scheduler-orchestration/skills/calendar-governance .agents/skills/calendar-governance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "calendar-governance" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/social-scheduler-orchestration/skills/calendar-governance into .agents/skills/calendar-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-governance", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gtmagents/gtm-agents --skill calendar-governance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gtmagents/gtm-agents calendar-governance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/social-scheduler-orchestration/skills/calendar-governance .cursor/skills/calendar-governance && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "calendar-governance" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/social-scheduler-orchestration/skills/calendar-governance into .cursor/skills/calendar-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-governance", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gtmagents/gtm-agents.git --path plugins/social-scheduler-orchestration/skills/calendar-governance--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gtmagents/gtm-agents --skill calendar-governance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gtmagents/gtm-agents calendar-governance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/social-scheduler-orchestration/skills/calendar-governance .gemini/skills/calendar-governance && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "calendar-governance" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/social-scheduler-orchestration/skills/calendar-governance into .gemini/skills/calendar-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-governance", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gtmagents/gtm-agents calendar-governanceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gtmagents/gtm-agents --skill calendar-governance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/social-scheduler-orchestration/skills/calendar-governance .github/skills/calendar-governance && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "calendar-governance" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/social-scheduler-orchestration/skills/calendar-governance into .github/skills/calendar-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-governance", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gtmagents/gtm-agents --skill calendar-governance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gtmagents/gtm-agents calendar-governance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/social-scheduler-orchestration/skills/calendar-governance .opencode/skills/calendar-governance && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "calendar-governance" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/social-scheduler-orchestration/skills/calendar-governance into .opencode/skills/calendar-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-governance", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
calendar-governance- GitHub stars
- 414
- Used in
- 1 other repo
- Token cost
- ~351 tokens
- SKILL.md length
- 149 words
- Files
- 1
- Skills in repo
- 121
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses to enforce cadence rules, timezone coverage, and operational controls on social calendars.
- Works in 5 steps: Cadence Rules – define min/max posts per… → Coverage & Localization – ensure global… → Dependency Checks – align with product… → …
- Enforce cadence rules
- SKILL.md covers When to Use, Framework, Templates and Tips
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Calendar Governance is an agent skill from gtmagents/gtm-agents. Use to enforce cadence rules, timezone coverage, and operational controls on social calendars.
Its SKILL.md is about 350 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Social media marketing. The repository describes itself as: Production-ready collection of GTM agents and specialized skills for claude code. Covers sales, marketing, customer success, and revenue operations workflows. The licence is Apache-2.0.
When your agent uses it
- Enforce cadence rules
- Timezone coverage
- Operational controls on social calendars
Example prompts
- “/calendar-governance”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Cadence Rules – define min/max posts per channel/day, quiet hours, and pacing relative to paid media.
- Coverage & Localization – ensure global timezones, languages, and partner regions have representation.
- Dependency Checks – align with product launches, events, newsletters, or PR activity to avoid clashes.
- Approval Milestones – map review deadlines backwards from publish times; include contingency buffers.
- Audit & Change Control – maintain version history, note last-minute overrides, and capture rationale.
What it can do on your machine
Read from SKILL.md and the folder at commit 78e0419. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Calendar Governance loads about 351 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 149 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from gtmagents/gtm-agents at commit 78e0419, republished under its Apache-2.0 licence (© gtmagents). 149 words, ~351 tokens.
Download SKILL.mdSave it as
.claude/skills/calendar-governance/SKILL.md (or your agent's skills folder).- name
- calendar-governance
- description
- Use to enforce cadence rules, timezone coverage, and operational controls on social calendars.
Social Calendar Governance Skill
When to Use
- Building or auditing cross-network publishing schedules.
- Coordinating regional calendars or blackout dates (events, outages, compliance windows).
- Running retros after missed posts or conflicting campaigns.
Framework
- Cadence Rules – define min/max posts per channel/day, quiet hours, and pacing relative to paid media.
- Coverage & Localization – ensure global timezones, languages, and partner regions have representation.
- Dependency Checks – align with product launches, events, newsletters, or PR activity to avoid clashes.
- Approval Milestones – map review deadlines backwards from publish times; include contingency buffers.
- Audit & Change Control – maintain version history, note last-minute overrides, and capture rationale.
Templates
- Calendar governance checklist (cadence, blackout, approvals, localization, dependencies).
- Timezone coverage heatmap (channel × region × daypart).
- Change-log template for late edits or cancellations.
Tips
- Publish a weekly "calendar health" snapshot for stakeholders.
- Pair with automation scripts that flag double-bookings or empty slots.
- Store governance docs alongside calendars for auditability.
© gtmagents, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/social-scheduler-orchestration/skills/calendar-governance of gtmagents/gtm-agents.
Open the folder on GitHubat commit 78e0419
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gtmagents/gtm-agents, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Calendar Governance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Calendar Governance this skillgtmagents/gtm-agents | 414 | 1 repos | ~351 | Automated safety check: Pass | Apache-2.0 | |
| Instagram Marketingsergebulaev/instagram-skills | 347 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Getxapi ConnectLeoYeAI/openclaw-marketing-skills | 1k | 1 repos | ~715 | Automated safety check: Pass | Custom licence | |
| Competitor Social ResearchScrapeCreators/social-media-research-skills | 3.4k | — | ~1.1k | Automated safety check: Notes | MIT | |
| Business Contact and Social Links Finderbrowser-act/skills | 6.1k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| LinkedIn Ads Managementivangfalco/ads-skills | 279 | — | ~1.7k | Automated safety check: Pass | Custom licence |
Similar skills
Getxapi Connect
LeoYeAI/openclaw-marketing-skills
Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.
Competitor Social Research
ScrapeCreators/social-media-research-skills
A skill your agent uses when the user wants to research competitors' social media strategy, compare brands or creators, find what content is working in a niche, identify content gaps, or produce a…
Business Contact and Social Links Finder
browser-act/skills
Finds a company's official website and social profiles from its name, or collects social links from a website URL, using BrowserAct templates run by a Python script.
LinkedIn Ads Management
ivangfalco/ads-skills
Routes LinkedIn Ads work for B2B SaaS to the right playbook: campaign planning, performance analysis, account audits, creative, scaling and account-based campaigns.
Buying Signal Monitor
unifapi-agent/agents
When a seller or SDR wants to catch public buying intent on X/Twitter and LinkedIn — someone asking for a tool they sell, complaining about or switching off a competitor, or hiring for a role that…
More from gtmagents/gtm-agents
All 121 skills in this repoEnrichment Data Sourcing
gtmagents/gtm-agents
Chooses and orders data providers for email, phone, company and intent enrichment, with waterfall sequences and credit-saving tactics across 150+ sources.
Cold Email Personalization
gtmagents/gtm-agents
Writes personalized B2B cold emails from prospect research, using a gated workflow, a quality rubric and follow-up sequences.
Discovery Call Playbook
gtmagents/gtm-agents
Structures sales discovery calls with a PREP routine, a five-part call flow, a question bank, a qualification scorecard and a follow-up recap email.
Lifecycle Mapping for Automation
gtmagents/gtm-agents
Frames marketing automation around lifecycle stages, signals, touches and SLAs, with worksheets for onboarding, expansion, renewal and churn-prevention journeys.
Social Selling
gtmagents/gtm-agents
A skill your agent uses when engaging prospects through LinkedIn, communities, and social channels to spark warm conversations and meetings.
Drip Campaigns
gtmagents/gtm-agents
A skill your agent uses when you need to map sequenced nurture flows with pacing, storytelling arcs, and value ladders.
Related
Categories
Questions about Calendar Governance
What does Calendar Governance do?
A skill your agent uses to enforce cadence rules, timezone coverage, and operational controls on social calendars. Calendar Governance is an agent skill from gtmagents/gtm-agents. Use to enforce cadence rules, timezone coverage, and operational controls on social calendars.
When should I use Calendar Governance?
Calendar Governance fits situations like: enforce cadence rules; timezone coverage; operational controls on social calendars.
How do I install Calendar Governance in Claude Code?
Run `npx skills add gtmagents/gtm-agents --skill calendar-governance -a claude-code`. Or copy the skill folder (plugins/social-scheduler-orchestration/skills/calendar-governance in gtmagents/gtm-agents) into .claude/skills/calendar-governance in your project. Claude Code loads it when a task matches its description.
How do I install Calendar Governance in Codex?
Run `npx skills add gtmagents/gtm-agents --skill calendar-governance -a codex`. Or copy the skill folder (plugins/social-scheduler-orchestration/skills/calendar-governance in gtmagents/gtm-agents) into .agents/skills/calendar-governance in your project. Codex loads it when a task matches its description.
Can I use Calendar Governance in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gtmagents/gtm-agents --skill calendar-governance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/calendar-governance, .gemini/skills/calendar-governance, .github/skills/calendar-governance and .opencode/skills/calendar-governance in your project.
What does Calendar Governance need to run?
SKILL.md names no scripts, command-line tools or credentials: Calendar Governance is instructions for the agent only.
Does Calendar Governance access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Calendar Governance safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Calendar Governance use?
Calendar Governance is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Calendar Governance use?
About 351 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Calendar Governance?
Skills that share tags, products or a category with Calendar Governance: Instagram Marketing (sergebulaev/instagram-skills, 347 stars), Getxapi Connect (LeoYeAI/openclaw-marketing-skills, 1k stars), Competitor Social Research (ScrapeCreators/social-media-research-skills, 3.4k stars) and Business Contact and Social Links Finder (browser-act/skills, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Calendar Governance?
gtmagents (a GitHub user) maintains it in gtmagents/gtm-agents, which has 414 GitHub stars. The repository holds 121 skills in this directory. The repository was last updated on April 3, 2026.
Source: gtmagents/gtm-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.