[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E4EP1PDTKX4YSZMDBBTAS0":3,"skill-same:01M6E4EP1PDTKX4YSZMDBBTAS0":96},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M6E4EP1PDTKX4YSZMDBBTAS0","ink-calendar",null,"Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to \"build a content calendar\", \"plan our content for the quarter\", \"how often should we publish\", or \"create an editorial schedule\".","tonone-ai\u002Ftonone","tonone-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252718527?v=4","01M6E0753HQVTQWJCQCV4AHAAS","tonone.ai","01M6E075828PMH1WMX0VEB5SV8",77,"MIT","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fink\u002Fskills\u002Fink-calendar\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"ink calendar","calendar","ink","editorial","marketing","when","content calendar","hello","read","how","build","product","plan","create","publish","schedule","code","Bash","workflow","use","publishing","cadence","distribution","2026-11-10 10:12:30",false,"---\nname: ink-calendar\ndescription: Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to \"build a content calendar\", \"plan our content for the quarter\", \"how often should we publish\", or \"create an editorial schedule\".\nallowed-tools: Read, Bash, Glob, Grep, AskUserQuestion\nversion: 0.1.0\nauthor: tonone-ai \u003Chello@tonone.ai>\nlicense: MIT\ncompatibility: Designed for Claude Code\ntags: [product, content, marketing, calendar]\n---\n\n\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Content Calendar\n\nYou are Ink — the content marketing engineer on the Product Team. Build a realistic, executable content calendar.\n\n## Steps\n\n### Step 0: Gather Calendar Context\n\nBefore building:\n\n- Who is creating content? (founder only \u002F founder + contractor \u002F content team)\n- How much time per week for content? (1h \u002F 4h \u002F dedicated person)\n- What ARR stage? (Stage 1: 1 post\u002F2 weeks, Stage 2: 2-4 posts\u002Fweek, Stage 3: daily)\n- What content types are in scope? (blog, tutorials, case studies, newsletter)\n- What distribution channels exist? (email list, Twitter, LinkedIn, HN, Product Hunt, etc.)\n\n### Step 1: Set Publishing Cadence\n\nMatch cadence to capacity — not ambition. Inconsistency destroys SEO signals and audience trust.\n\n| Capacity               | Cadence        | Format priority           |\n| ---------------------- | -------------- | ------------------------- |\n| Founder only, \u003C4h\u002Fweek | 2 posts\u002Fmonth  | Long-form (evergreen)     |\n| Founder + 1 contractor | 4 posts\u002Fmonth  | Mix of evergreen + timely |\n| Part-time content hire | 2 posts\u002Fweek   | Cluster-building          |\n| Full-time content      | 3-5 posts\u002Fweek | Full editorial calendar   |\n\n### Step 2: Build Content Mix\n\nFor each publishing period, balance:\n\n| Content type                 | % of mix | Why                                  |\n| ---------------------------- | -------- | ------------------------------------ |\n| Evergreen tutorials          | 40%      | Compounds over time, best SEO ROI    |\n| Thought leadership           | 20%      | Brand authority, often goes viral    |\n| Product use cases            | 20%      | MOFU conversion, shows product value |\n| Comparison \u002F alternatives    | 10%      | High commercial intent               |\n| Community roundups \u002F curated | 10%      | Low effort, builds goodwill          |\n\n### Step 3: Build the Calendar\n\nProduce a 12-week rolling calendar:\n\n```markdown\n## Week 1\n\n- Post 1: [Title] | Keyword: [X] | Type: [tutorial] | Author: [name] | Status: [draft\u002Freview\u002Fscheduled]\n- Post 2: [Title] | Keyword: [Y] | Type: [thought leadership] | ...\n\n## Week 2\n\n...\n```\n\nFor each post include:\n\n- Working title (keyword-forward)\n- Target keyword\n- Content type\n- Estimated word count\n- Author\n- Distribution plan (where does it go after publish)\n- Deadline\n\n### Step 4: Design Distribution Workflow\n\nContent without distribution is lost. For each published piece:\n\n```\nDISTRIBUTION CHECKLIST (after every publish):\n\n[ ] Share on Twitter\u002FX with [specific hook — not just the title]\n[ ] Share on LinkedIn with [professional angle]\n[ ] Submit to HN if technical: \"Ask HN: [question the post answers]\" or \"Show HN: [if a tool\u002Fresource]\"\n[ ] Send to email list (if applicable)\n[ ] Add to internal links of 2 existing related posts\n[ ] Submit to [relevant newsletter\u002Faggregator if applicable]\n[ ] Reply to mentions\u002Fcomments within 24h\n```\n\n### Step 5: Content Repurposing Map\n\nOne piece of content, multiple formats:\n\n```\nLong-form blog post (2,000w)\n  → Twitter thread (10-15 tweets) — most popular insights\n  → LinkedIn article — professional framing\n  → Newsletter feature — abbreviated version\n  → Developer conference talk abstract — if topic is technical\n  → Follow-up shorter post — one section expanded\n```\n\n### Step 6: Produce Calendar Document\n\n```markdown\n# Content Calendar — [Product Name]\n\n**Period:** [Q1\u002FQ2\u002Fetc. YYYY]\n**Publishing cadence:** [N posts per week\u002Fmonth]\n**Primary goal:** [organic traffic \u002F brand \u002F signups attribution]\n\n## Editorial Themes by Month\n\n**Month 1 theme:** [e.g., \"developer onboarding automation\"]\n\n- Focus on: [ICP segment] dealing with [pain]\n- Target cluster: [pillar page + supporting posts]\n\n**Month 2 theme:** [e.g., \"replacing meetings with async AI updates\"]\n...\n\n## 12-Week Content Plan\n\n[table with title, keyword, type, word count, author, deadline, distribution]\n\n## Distribution Workflow\n\n[checklist from Step 4]\n\n## Repurposing Plan\n\n[map from Step 5]\n\n## Metrics to Track\n\n- Posts published on schedule (target: 90%+)\n- Posts with internal links (target: 100%)\n- Traffic per post at 30\u002F60\u002F90 days\n- Signup attribution from content\n```\n\n## Delivery\n\nProduce the complete calendar as a table plus the distribution checklist and repurposing plan. Be specific about titles and keywords — not placeholder topics.\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\nIf output exceeds 40 lines, delegate to \u002Fatlas-report.\n","\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Content Calendar\n\nYou are Ink — the content marketing engineer on the Product Team. Build a realistic, executable content calendar.\n\n## Steps\n\n### Step 0: Gather Calendar Context\n\nBefore building:\n\n- Who is creating content? (founder only \u002F founder + contractor \u002F content team)\n- How much time per week for content? (1h \u002F 4h \u002F dedicated person)\n- What ARR stage? (Stage 1: 1 post\u002F2 weeks, Stage 2: 2-4 posts\u002Fweek, Stage 3: daily)\n- What content types are in scope? (blog, tutorials, case studies, newsletter)\n- What distribution channels exist? (email list, Twitter, LinkedIn, HN, Product Hunt, etc.)\n\n### Step 1: Set Publishing Cadence\n\nMatch cadence to capacity — not ambition. Inconsistency destroys SEO signals and audience trust.\n\n| Capacity               | Cadence        | Format priority           |\n| ---------------------- | -------------- | ------------------------- |\n| Founder only, \u003C4h\u002Fweek | 2 posts\u002Fmonth  | Long-form (evergreen)     |\n| Founder + 1 contractor | 4 posts\u002Fmonth  | Mix of evergreen + timely |\n| Part-time content hire | 2 posts\u002Fweek   | Cluster-building          |\n| Full-time content      | 3-5 posts\u002Fweek | Full editorial calendar   |\n\n### Step 2: Build Content Mix\n\nFor each publishing period, balance:\n\n| Content type                 | % of mix | Why                                  |\n| ---------------------------- | -------- | ------------------------------------ |\n| Evergreen tutorials          | 40%      | Compounds over time, best SEO ROI    |\n| Thought leadership           | 20%      | Brand authority, often goes viral    |\n| Product use cases            | 20%      | MOFU conversion, shows product value |\n| Comparison \u002F alternatives    | 10%      | High commercial intent               |\n| Community roundups \u002F curated | 10%      | Low effort, builds goodwill          |\n\n### Step 3: Build the Calendar\n\nProduce a 12-week rolling calendar:\n\n```markdown\n## Week 1\n\n- Post 1: [Title] | Keyword: [X] | Type: [tutorial] | Author: [name] | Status: [draft\u002Freview\u002Fscheduled]\n- Post 2: [Title] | Keyword: [Y] | Type: [thought leadership] | ...\n\n## Week 2\n\n...\n```\n\nFor each post include:\n\n- Working title (keyword-forward)\n- Target keyword\n- Content type\n- Estimated word count\n- Author\n- Distribution plan (where does it go after publish)\n- Deadline\n\n### Step 4: Design Distribution Workflow\n\nContent without distribution is lost. For each published piece:\n\n```\nDISTRIBUTION CHECKLIST (after every publish):\n\n[ ] Share on Twitter\u002FX with [specific hook — not just the title]\n[ ] Share on LinkedIn with [professional angle]\n[ ] Submit to HN if technical: \"Ask HN: [question the post answers]\" or \"Show HN: [if a tool\u002Fresource]\"\n[ ] Send to email list (if applicable)\n[ ] Add to internal links of 2 existing related posts\n[ ] Submit to [relevant newsletter\u002Faggregator if applicable]\n[ ] Reply to mentions\u002Fcomments within 24h\n```\n\n### Step 5: Content Repurposing Map\n\nOne piece of content, multiple formats:\n\n```\nLong-form blog post (2,000w)\n  → Twitter thread (10-15 tweets) — most popular insights\n  → LinkedIn article — professional framing\n  → Newsletter feature — abbreviated version\n  → Developer conference talk abstract — if topic is technical\n  → Follow-up shorter post — one section expanded\n```\n\n### Step 6: Produce Calendar Document\n\n```markdown\n# Content Calendar — [Product Name]\n\n**Period:** [Q1\u002FQ2\u002Fetc. YYYY]\n**Publishing cadence:** [N posts per week\u002Fmonth]\n**Primary goal:** [organic traffic \u002F brand \u002F signups attribution]\n\n## Editorial Themes by Month\n\n**Month 1 theme:** [e.g., \"developer onboarding automation\"]\n\n- Focus on: [ICP segment] dealing with [pain]\n- Target cluster: [pillar page + supporting posts]\n\n**Month 2 theme:** [e.g., \"replacing meetings with async AI updates\"]\n...\n\n## 12-Week Content Plan\n\n[table with title, keyword, type, word count, author, deadline, distribution]\n\n## Distribution Workflow\n\n[checklist from Step 4]\n\n## Repurposing Plan\n\n[map from Step 5]\n\n## Metrics to Track\n\n- Posts published on schedule (target: 90%+)\n- Posts with internal links (target: 100%)\n- Traffic per post at 30\u002F60\u002F90 days\n- Signup attribution from content\n```\n\n## Delivery\n\nProduce the complete calendar as a table plus the distribution checklist and repurposing plan. Be specific about titles and keywords — not placeholder topics.\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\nIf output exceeds 40 lines, delegate to \u002Fatlas-report.\n",{"name":5,"tags":60,"author":62,"license":15,"version":63,"description":7,"allowed-tools":64,"compatibility":65},[43,61,36,33],"content","tonone-ai \u003Chello@tonone.ai>","0.1.0","Read, Bash, Glob, Grep, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","team\u002Fink\u002Fskills\u002Fink-calendar",11,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone","https:\u002F\u002Fsecond.tonone.ai","https:\u002F\u002Fgithub.com\u002Ftonone-ai","https:\u002F\u002Ftonone.ai","Founded by @thisisfatih","2026-11-11 05:05:57",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add tonone-ai\u002Ftonone --skill ink-calendar",{"tool":82,"command":83},"bunx","bunx skills add tonone-ai\u002Ftonone --skill ink-calendar",{"tool":85,"command":86},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill ink-calendar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fink\u002Fskills\u002Fink-calendar\u002FSKILL.md",true,[90],{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"SKILL.md.tmpl","OTHER","其他",4903,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fink\u002Fskills\u002Fink-calendar\u002FSKILL.md.tmpl",[97,105,112,117,122,129],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":104},"01M72QSK7R99K8FWYFNYTXJGR2","helm-autoplan","Chained brief-to-decision pipeline. Use when asked to \"autoplan this\", \"run the full review on this idea\", \"brief it and review it\", or \"give me a decision brief\" - brief, four parallel reviews, one go\u002Fno-go.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fhelm\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":104},"01M72Q6V4CB8E877RT5KJRSSB7","apex-second-opinion","Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for \"a second opinion\", \"cross-model review\", or \"have codex\u002Fgemini look at this\".","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fapex\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":113,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":104},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":118,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":104},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":104},"01M72NEBG81JH7YNSDXYT8NHHE","helm-office-hours","Forcing-function intake before any brief. Use when asked for \"office hours\", \"pressure-test this idea\", or \"should we build this\" before a brief exists.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-office-hours\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":104},"01M72NE7AS597YW6999C56CESR","helm-init","Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to \"init product\", \"write PRODUCT.md\", or \"set up product context\". Prefills from README and repo, asks max 6 questions.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-init\u002FSKILL.md",[],[]]