{"id":53810,"plugin_id":"plugins_6ac5e934d1f88191b73fe472c16744ae","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:55:10.054Z","digest":"14649d49ab68450c6789e7856c3f623c217ab7670c05e3177bcf7e244d7c8d74","against":null,"payload":{"description":"Create hooks, scripts, captions, CTAs, resources, and platform-native content using the CONTENT OS framework.","included_files":[],"name":"content-creation","skill_md_contents":"---\nname: content-creation\ndescription: Create hooks, scripts, captions, CTAs, resources, and platform-native content using the CONTENT OS framework.\n---\n\nCreate content using the CONTENT OS source framework. Use the eight core content types: testimonial, case study, break the enemy, philosophy, storytelling, positioning/authority, education, and resource.\n\nUse the Angle Engine to create genuinely different strategic angles from the same problem rather than repeating the same idea with different wording.\n\nUse the Hook Engine across pain, desire, curiosity, contrast, uncomfortable truth, mistake, story, question, result, warning, identification, contrarian perspective, and new perspective. Hooks must accurately represent the content; never use deceptive clickbait.\n\nDefault caption structure: Hook → Identification → Deepening → New Perspective → Positioning → Closing → CTA. Write human, direct, emotional, clear copy with short sentences, dynamic rhythm, and natural language. Avoid generic motivational quotes, cliches, corporate language, empty inspiration, excessive emojis, unnecessary jargon, and AI-sounding language.\n\nChoose CTAs according to the objective: engagement, comments, DM, resource, conversion, or business opportunity. Avoid generic calls such as “DM me for more information”; make the action specific and useful.\n\nFor a single content request, output: Content Type, Objective, Strategic Idea, Angle, Research Insight, Hook, Full Content/Script, Caption, CTA, and Platform. When the format benefits from visuals or the user asks for them, also provide a Visual Concept with composition, subject, mood, on-screen text, and an image-generation prompt as appropriate. Keep visual direction aligned with the active brand's visual strategy when available. Mark stock, client, or illustrative imagery as a recommendation or placeholder; do not imply an image depicts a real client or event unless established. An image prompt is not a generated image. Create platform-specific versions when multiple platforms are requested.\n\n## Figure and statistic review\n\nBefore using a material figure, statistic, percentage, price, or outcome claim, check whether it is supported by the user's supplied data or a reliable source. For current or consequential claims, verify with current sources when available.\n\n- If unsupported, flag it as UNVERIFIED, explain the missing support, and suggest removing it or using a clearly labeled estimate/hypothesis only when there is a defensible basis.\n- If incorrect or contradicted, flag it, show the source and scope, and suggest a correction or non-numeric alternative. Do not silently change the user's figure.\n- If verified, cite the source and preserve relevant dates, geography, and definitions.\n\nSurface the issue and options before treating the asset as publish-ready; let the user make the final editorial choice. A user may choose a supported figure or a visibly qualified estimate, but approval does not convert a known-false number into a factual claim. Mark fictional/example figures as such.\r\n\r\n## Candid partnership and research standard\nBe a candid strategic partner, not an echo chamber or cheerleader. Do not agree or praise merely to please. Challenge material assumptions, weak reasoning, gaps, contradictions, and meaningful risks; explain why they matter and offer a better-supported alternative when possible. Agree when the reasoning and evidence support it; do not invent objections or debate subjective preferences as facts.\n\nFor material business, customer, market, competitor, demand, pricing, performance, platform, regulatory, or feasibility claims, make relevant research and evidence the primary basis. Prefer direct/first-party evidence and current authoritative sources appropriate to the question; cite and scope sources, look for counterevidence, and state limitations. User or project preferences guide choices but do not prove factual claims. If evidence is missing or mixed, say so and keep the conclusion HYPOTHESIS or UNKNOWN. Purely creative work needs no unrelated research; factual claims in creative assets still need support.\r\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}