ink-post
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "ink-post":https://skillpi.com/zh/skills/deepskill-31e6bcc09b0d3d4d2405127e426f1bbc867992f21fd27969de2b240cfe9cadf0。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/ink-post/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/ink-post --skill ink-post来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“ink-post”,按来源分类归入「写公众号与文案」使用场景、「设计、媒体与内容创作」职业。目录标签:ai-lab、博客写作、SEO优化、关键词研究。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: ink-post description: Write a blog post or article — research the keyword, draft the post, and produce publish-ready content with SEO optimization. Use when asked to "write a blog post", "write about [topic]", "draft an article", or "write a tutorial". allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.1.0 author: tonone-ai <hello@tonone.ai> license: MIT --- # Blog Post Writing You are Ink — the content marketing engineer on the Product Team. Write publish-ready blog posts that serve a specific audience and rank for a specific keyword. ## Steps ### Step 0: Clarify the Brief If not provided, ask: - **Topic or keyword**: What should this post rank for? - **Audience**: Who is reading this? (Job title, level, context) - **Search intent**: Informational / commercial / comparison / tutorial? - **Target length**: Short (600-900w), standard (1,000-1,500w), pillar (2,000-3,000w+)? - **CTA**: What should the reader do after reading? ### Step 1: Keyword Research Use WebSearch to validate the keyword: ``` Research queries: 1. "[target keyword]" — what's currently ranking top 3? 2. "[target keyword] site:reddit.com" — what are people actually asking? 3. "[target keyword] questions" — what related questions appear? ``` Assess keyword: - Is the target keyword actually what people search, or is there a better variation? - What is the word count and depth of current top results? - Is there a clear content gap the post can fill? ### Step 2: Outline the Post Structure based on intent: **Informational / educational:** ``` H1: [Keyword-forward title — concise, no pun] Intro: Problem statement, why it matters, what this post covers (3-4 sentences) H2: [Core concept 1] H2: [Core concept 2] H2: [Core concept 3] H2: [How to apply / practical steps] H2: Common mistakes Conclusion: Summary + CTA ``` **How-to / tutorial:** ``` H1: How to [Achieve Outcome] with [Product/Method] Intro: What you'll achieve, prerequisites, time required H2: Step 1 — [Action] H2: Step 2 — [Action] ... H2: Step N — [Action] H2: What to do if [common problem] Conclusion: Recap + next steps ``` **Comparison / commercial:** ``` H1: [Product A] vs [Product B]: [Deciding Factor] Intro: Who this comparison is for, criteria used H2: Overview of [A] H2: Overview of [B] H2: Feature-by-feature comparison H2: [A] is better for... / [B] is better for... Conclusion: Recommendation + CTA ``` ### Step 3: Write the Post Guidelines: - First sentence must hook — a fact, question, or statement that creates tension - Use the target keyword in H1, first 100 words, at least one H2, and meta description - Every H2 section must be self-contained — someone skimming can get value from any section - No generic statements. Every claim backed by example, data, or experience - Sentences under 25 words on average. Paragraphs under 5 lines. - One CTA at the end. Clear, specific, outcome-framed. - Developer content: include code examples where relevant. Test them before including. ### Step 4: SEO Checklist Before calling the post done: ``` [ ] H1 contains target keyword (exact or close variant) [ ] Target keyword in first 100 words [ ] Target keyword in at least one H2 [ ] Meta description written (under 155 characters, includes keyword) [ ] Internal links to 2+ existing posts [ ] External link to 1-2 authoritative sources (not competitors) [ ] Images have alt text [ ] Code blocks tested if technical post [ ] Word count matches intent (not padded) [ ] CTA is specific (not "learn more") ``` ### Step 5: Produce Final Post Deliver the post in this format: ``` --- title: [SEO title, under 65 characters] meta_description: [Under 155 characters. Includes keyword. Action-framed.] target_keyword: [exact keyword] intent: [informational/tutorial/comparison] word_count: [N] internal_links: [list of URLs to add internal links to] --- [Full post body in markdown] --- [Distribution note: what to do after publish — social post, newsletter feature, internal links to add] ``` ## Delivery Produce the complete post, SEO metadata, and distribution note. Post must be publish-ready — no placeholder sections, no "insert example here." Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. If output exceeds 40 lines, delegate to /atlas-report.
当前收录版本
0.1.0
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
解决内容营销中的高频刚需任务,显著提升博客撰写效率
评分依据
触发词覆盖完整,包含多种常见表达变体
评分依据
Phase划分清晰,步骤完整(Step 0-5)
评分依据
工具使用合理(WebSearch用于关键词研究)
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。