AGENT SKILL

appie-article-writer

Write short light articles or long deeply-researched articles with Appie.run Content Writer. Use when the user asks to write an article, generate a blog post, create deeply researched content, draft in an author voice, or check article status. Triggers include write a short article, deeply researched piece, blog post about, generate content in my voice, article status.

License 许可
MIT
所属仓库
bg-szy/TOP-SKILLS
最近更新
2026-11-15
Stars
★ 6
Forks
0

01 前言 Front Matter

name
appie-article-writer
license
MIT
description
Write short light articles or long deeply-researched articles with Appie.run Content Writer. Use when the user asks to write an article, generate a blog post, create deeply researched content, draft in an author voice, or check article status. Triggers include write a short article, deeply researched piece, blog post about, generate content in my voice, article status.

02 资源文件 1

03 SKILL.md 正文

Appie Article Writer

Overview

Generate articles in a chosen author voice via Appie.run Content Writer.

  • light — ~500 words, 100 credits
  • deeply_researched — ~3000 words, 500 credits

Generation is asynchronous. Always poll status. Never invent article content — only return what the API provides.

Prerequisites (always run first)

This skill needs the Appie.run MCP server connected to your agent.

  1. Check whether the Appie tools (e.g. create_article, list_authors) are already available. If they are, continue.
  2. If not, ask the user to connect the Appie MCP server:
    • URL: https://appie.run/mcp (transport: streamable HTTP)
    • Header: Authorization: Bearer <esk_...> (your Appie.run project API key, starting with esk_)
    • Setup docs for each client: https://appie.run/docs/mcp
  3. New Appie.run accounts get 500 free credits. Never ask the user to paste their key into chat, and never invent one. Stop and wait until the tools are available before continuing.

Tool Reference

Action Tool name Cost Notes
List authors list_authors free Check readiness
Create author create_author free bio ≥50 chars
Add author sample add_author_sample free content ≥100 chars or blog_url
Create article create_article 100 / 500 charged on generation
Article status article_status free poll until ready
Get brain get_brain free brand context (auto-used)
Update brain update_brain free only if user asks

create_article parameters

Note: create_article fails with author_profile_required until an author exists. Create one with create_author first (or check with list_authors).

  • topic (required) — clear description of the article subject
  • article_type — "light" (default) or "deeply_researched"
  • author_id (optional integer) — omit to use the project's active author

create_author parameters

  • author_name (required)
  • bio (required, ≥50 characters)
  • is_active (optional boolean, default true)
  • sample_title / sample_content (optional, sample_content ≥100 chars)

Full Workflow

1. Clarify type and topic

  • If the user says only "write an article", ask whether they want light (~500 words, 100 credits) or deeply_researched (~3000 words, 500 credits).
  • Confirm the exact topic if ambiguous.

2. Ensure a usable author

  1. Call list_authors.
  2. Prefer an author marked ready / active.
  3. If none exist or the desired voice is missing:
    • Create one with create_author (bio ≥50 chars).
    • Optionally add a writing sample (≥100 chars) via add_author_sample so the voice is stronger.
  4. If an author exists but is not ready, add a sample and re-check.

3. Start generation

  1. Call create_article with topic, chosen article_type, and optional author_id.
  2. Immediately tell the user:
    • The article id
    • Expected cost
    • That generation is running in the background
  3. Capture the returned id for polling.

4. Poll until ready

  1. Call article_status with the id.
  2. Repeat every few turns or when the user asks "is it ready?" until content appears or status is failed/complete.
  3. On success, return the full article text, title (if provided), id, and type.
  4. On failure, surface the exact error message and stop.

5. Optional Brain context

  • Call get_brain if the user wants to inspect brand voice, ICP, competitors, or key messages.
  • Only call update_brain when the user explicitly requests brand or ICP changes.
  • Content Writer already uses Brain context automatically; you do not need to inject it.

Error Handling & Edge Cases

  • create_article fails with author_profile_required until the project has an author → check with list_authors, create one with create_author (bio ≥50 chars), then retry.
  • Author not ready → add sample (≥100 chars) then retry create_article.
  • Insufficient credits → report the exact cost (100 or 500) and stop. Do not start generation.
  • Ambiguous topic → ask one clarifying question before calling create_article.
  • Multiple authors → list them and let the user choose, or use the active one if the user does not care.
  • Generation stuck / failed → show the status payload and offer to start a new article with a refined topic.
  • Never invent or paraphrase the article body. Quote or present the exact content returned by article_status.
  • If the user later wants the same article fed into a chatbot, note the article_id for the appie-chatbot skill.

Response Style

  • State cost and async nature up front.
  • After creation, give the id and offer to check status.
  • When ready, deliver the full content cleanly (preserve headings and structure).
  • Keep follow-up questions minimal and focused.

04 同仓库更多 Skills

bg-szy
bg-szy/TOP-SKILLS

serpmaven

Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-landing-page-audit

Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-growth-context

Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-get-listed

Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-ai-readiness-audit

Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

proxy-troubleshooting

Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.

★ 6