Agent skill
week-posts
Plan and draft a week of content using the author's configured pillars, source material, voice, cadence and optional Notion board.
Filed under Outbound email.
From timscheuerai/gtm-architecture-template · 51 skill entries · 13 · pushed 2026-09-17
What it does when it runs
Plan and draft a week of content using the author's configured pillars, source material, voice, cadence and optional Notion board.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/timscheuerai/gtm-architecture-template.git /tmp/gtm-architecture-template git -C /tmp/gtm-architecture-template sparse-checkout set ".agents/skills/week-posts" mkdir -p ~/.claude/skills/week-posts cp -R "/tmp/gtm-architecture-template/.agents/skills/week-posts/." ~/.claude/skills/week-posts/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from timscheuerai/gtm-architecture-template/blob/2c312c9398064ad3730c786647293458cb89632c/.agents/skills/week-posts/SKILL.md, which is licensed MIT (repository). 375 words, 3 headings.
Workspace: all context paths below (identity, audience, strategy, voice, brand, raw, output, index, log, workspace preferences and context scripts) resolve from context/ in the kit root. Read both the root AGENTS.md and context/AGENTS.md. Skill-local references/ and flowchart scripts/ resolve from this skill directory.
Plan the week
Read AGENTS.md, index.md, the relevant identity and audience pages, identity/proof.md, strategy/goals.md, strategy/pillars.md, strategy/funnel.md and voice/linkedin-voice.md. Read local preferences if present.
Choose the dates and material
Use the requested dates, time zone, platform and cadence. Do not inherit a particular founder's weekdays or a fixed four-post schedule. If the user wants a dated plan and the time zone or cadence is unknown, ask for those choices together. An undated draft batch can proceed without them.
Read the configured Notion taxonomy, topic page-body subtopics, recent published content and future cards when available. Otherwise use the local strategy and supplied history. Do not claim recent topics are unused when history is inaccessible.
Select distinct source-backed angles and an appropriate pillar mix. One per pillar is a useful option, not a mandate. Avoid repeating a recent idea unless the new post has a clear new contribution. Pick one pillar, topic, subtopic and funnel job for each piece. Do not silently create a new taxonomy to fill a slot.
If key material is missing, complete the supported part of the plan and identify the source needed for the rest. Do not fabricate posts to hit a count.
Draft and save
Use the local linkedin-copywriter skill for LinkedIn pieces. Other platforms use the configured format and voice rules. Keep proof and conversion targets grounded.
A request to draft a week into the board authorizes creating draft cards in the configured board. Follow strategy/notion-schema.md; query existing dates and titles first. Use Status = Creating, one Pillar value, Platform, planned Publish date and one paste-ready text code block in each card. After an ambiguous result, query before retrying.
Without Notion, return the plan and drafts in chat. Do not start a local posts database or pretend cards were saved.
Report date, pillar, topic, funnel job and card link where created. State which content is still waiting on input. Log the run without duplicating post copy. A planned date is not a scheduled publishing action.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- playbook-social-posts by growthenginenowoslawski · 759
- playbook-social-posts by automatewithuday · 1
- linkedin-posts-summary by jurjen-gtm-engineer · 0
Need help setting it up?
This page tells you what week-posts does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.