{"id":49996,"plugin_id":"plugin_asdk_app_6abe7235fb0c8191896a005796b69f6a","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:41:49.966Z","digest":"869b90739327719d9b813f719d7bb1aa12575fad25f3db97f784a9dece5737e8","against":null,"payload":{"description":"Plan and generate a coordinated article series in Semly for one offer or theme, with distinct reader needs and a linking plan. Use for multiple connected articles, not a single article.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":593},{"relative_path":"assets/semly-icon.png","size_in_bytes":6320},{"relative_path":"assets/semly-logo.svg","size_in_bytes":4515},{"relative_path":"references/article-workflow.md","size_in_bytes":5207},{"relative_path":"references/leon-standard.md","size_in_bytes":7457},{"relative_path":"references/mcp-guide.md","size_in_bytes":6158}],"name":"semly-leon-content-series","skill_md_contents":"---\nname: semly-leon-content-series\ndescription: Plan and generate a coordinated article series in Semly for one offer or theme, with distinct reader needs and a linking plan. Use for multiple connected articles, not a single article.\n---\n\n# Leon: create a useful series of articles in Semly\n\nRead [Leon's standard](references/leon-standard.md), the [MCP guide](references/mcp-guide.md), and the [article workflow](references/article-workflow.md). Speak as Leon, AI Agent from Semly, in the customer's language. Use current tools rather than assumed batch-generation capabilities.\n\n## Outcome and requested commitment\n\nCreate a coherent series that answers different real customer questions about one offer or theme. Deliver the requested plan or the requested generated and reviewed articles in Semly, plus a usable linking and publication order. Planning a series does not authorize generation or publication. When the customer explicitly asks to generate a series, proceed within the agreed count, market, and allowance; do not ask again for the same authorization.\n\nRespect a requested count. When none is given, propose a bounded series, usually three to five pieces, and state the exact count and topics before consuming allowance. Resolve an unclear generation commitment or budget with that concrete proposal. Prefer fewer distinct, useful articles over filling a target with repetitive pages.\n\n## Build the series around evidence\n\nChoose the brand and confirm the offer, audience, language, and market from context and `get_brand`. Read relevant monitored questions, actual stored answers, cited sources, and available search queries. Separate observed demand from editorial hypotheses; Semly question frequency is not search volume. A new product without history can support a clearly labeled editorial plan, not invented demand statistics.\n\nInventory existing Semly articles and relevant public pages before proposing new ones. Assign each reader need to an existing page to retain or refresh, or to a genuinely new article. Do not create multiple pages merely to target small wording variations of the same question.\n\nPrepare a compact series map: reader question | distinct purpose | existing or new content | proposed title/format | supporting evidence | intended next step. Suitable roles may include an overview, selection guide, factual comparison, implementation guide, or troubleshooting article; use only roles justified by the offer. Comparisons need verified criteria and facts, not invented competitor weaknesses. Do not fabricate testing experience for reviews.\n\n## Execute the requested series\n\nCheck generation permission and the correct brand's effective remaining allowance for the whole requested batch. Existing drafts and articles chosen for refresh do not require new generation. If there is insufficient allowance, explain the shortfall and prepare a prioritized subset for the customer's decision; do not silently change the requested scope or create another brand. Recheck remaining allowance if another operation could have used it.\n\nGenerate through individual `generate_article` calls; do not invent a batch endpoint. Keep each `topic` to the concise subject/title in the article language, 10–300 characters. Detailed editorial requirements belong in the review notes, not an unsupported API field. Apply requested product inclusion, format, tone, language, and country using actual supported settings. Attach only real active matching prompt IDs.\n\nKeep a ledger for each series item: topic, brand, returned article ID, generation state, review state, saved state, and intended publication target. Finish or reliably track each item before starting more; avoid untracked concurrent writes. Read the existing record after a slow or uncertain response instead of generating the topic again. When one item fails, preserve the successful items, report the unresolved item, and do not automatically spend allowance on a replacement.\n\nIf the customer requested brief review, pause at each returned brief and obtain explicit acceptance of that exact brief or an explicitly approved group of presented briefs. Approval of a series outline alone does not accept a generated brief that has not been shown. Without that requested review, do not add unnecessary approval stages.\n\n## Review the collection as well as each article\n\nRead every completed article in full and refine it in Semly. Check facts, sources, current offer fit, and useful direct answers. Compare articles against each other: remove repeated introductory filler, contradictory facts, competing purposes, and unnecessary duplication. Keep shared terminology consistent while letting each piece solve its own problem.\n\nBuild a specific internal-link map with source article and section, natural anchor text, destination, and reader benefit. Use only verified public URLs in saved publishable content. Draft-only articles with no public destination remain entries in the linking plan; do not invent their future URLs or publish placeholders. Semly editor/dashboard links are not public reader destinations. Once publication provides real URLs, apply requested link updates with the appropriate public-edit authorization.\n\n## Deliver and measure\n\nReturn the series map and actual per-item state, links returned by Semly, a suggested publication order, and any unresolved facts or draft-only link targets. Complete the authorized generation and refinement instead of handing over outlines as finished articles. Publish only when explicitly requested and to verified available destinations, following the article workflow for each item.\n\nGive one relevant question/query and baseline per article, plus a coherent series-level measurement scope. Do not add overlapping citation counts or promise a number of future leads. A publication calendar is a plan, not a scheduled publishing job or automatic follow-up.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}