# createskills Full AI Context Corpus This generated Markdown corpus is for AI agents, answer engines, and source discovery. It complements /llms.txt, /sitemap.xml, and normal HTML pages. It is not a Google ranking shortcut. ## Product Summary createskills captures web pages, videos, links, PDFs, images, and social media posts as clean Markdown, organizes them into a reusable source feed, and exposes saved captures to AI agents through hosted MCP. - Chrome extension: https://chromewebstore.google.com/detail/web-to-markdown-converter/baldeecdnlomdeedfddlnakmbhpeomgc - iPhone app: https://apps.apple.com/app/createskills/id6763325282 - Sitemap: https://www.createskills.io/sitemap.xml - Short llms file: https://www.createskills.io/llms.txt ## Core Pages - [Web to Markdown Browser Extension + MCP Server](https://www.createskills.io/): Homepage for the createskills browser extension, hosted MCP server, AI-agent Markdown capture workflows, pricing, and curated skill kits. - [Changelog](https://www.createskills.io/changelog): Public product updates for the createskills web app, extension, and iPhone app. - [Resources](https://www.createskills.io/resources): Index of createskills resource pages covering source capture, Markdown extraction, integrations, and AI workflow use cases. - [AI Workflow Skill Kits for Creators and Founders](https://www.createskills.io/kits): Catalog of createskills curated AI workflow skill kits for creators, founders, and marketers, including outcomes, audiences, source counts, provenance notes, and coming-soon purchase status. - [Privacy Policy](https://www.createskills.io/privacy): Privacy policy covering account data, source capture, kit entitlements, billing, and platform-specific disclosures. - [Terms of Service](https://www.createskills.io/terms): Terms for using createskills, including source-library credits, curated kits, acceptable use, and billing. # SEO and Workflow Pages ## AI skill generator for agent workflows - URL: https://www.createskills.io/ai-skill-generator - Category: tool - Primary keyword: AI skill generator - Updated: 2026-05-04 An AI skill generator converts trusted source material into reusable instructions and reference files that an agent can load when a task calls for that context. ### Sections #### What createskills generates The output is a plain-file skill package, not a locked database. Each zip contains an editable SKILL.md file plus a references/ folder with the Markdown, transcript, PDF, image, or source notes you captured. - SKILL.md explains when the agent should use the skill and how it should work. - references/ stores the source material so the agent can inspect the original context. - The zip can be reviewed, edited, committed, uploaded, or shared like normal files. #### Why this is different from a prompt A prompt is usually one-off text pasted into a chat. A skill is reusable context with a name, trigger, workflow, and source files. That makes it better for repeatable work like reviewing pull requests, writing in a brand voice, summarizing research, or following a specific content playbook. #### Best source mix The strongest skills combine instructions with evidence. A useful marketing skill might include a brand guide, high-performing emails, customer reviews, and competitor pages. A coding skill might include framework docs, architecture notes, GitHub issues, and examples from the repo. #### Ownership and review Because the output is plain Markdown and files, you can inspect every line before giving it to an AI tool. That matters when skills are allowed to influence code, campaigns, research, or client-facing work. ### Proof and Limitations #### Transparent output The generated package is intentionally inspectable: a SKILL.md file, source references, and normal folders instead of a hidden builder state. - Review SKILL.md before installing it in an agent workflow. - Delete weak references before packaging a skill. - Keep source URLs in reference files for claim tracing. #### Current limitation createskills prepares source-backed skill folders. Final quality still depends on source selection, target-agent support, and human review before reuse. ### Workflow Example workflow 1. Capture a product doc, a YouTube walkthrough, and a PDF brief. 2. Review the cleaned Markdown in the createskills feed. 3. Add the sources to a bucket named product-launch-skill. 4. Generate a zip with SKILL.md and references/ files. 5. Upload or place the files where your AI tool can read them. ### Sample ```text product-launch-skill.zip ├─ SKILL.md └─ references/ ├─ product-doc.md ├─ youtube-walkthrough.md └─ launch-brief.pdf ``` ### FAQ Q: What is an AI skill? A: An AI skill is a reusable package of instructions and references that helps an agent perform a specific type of task with better context. Q: What is SKILL.md? A: SKILL.md is the main instruction file. It describes the skill, when to use it, and how the agent should use the attached references. Q: Which agents can use the output? A: Any tool that accepts Markdown files or uploaded project files can use the context. Tools with Agent Skills support can use the SKILL.md structure more directly. Q: Can I edit the skill before using it? A: Yes. The package is plain files, so you can edit SKILL.md, rename references, delete sources, or add your own notes before using it. ### Related - https://www.createskills.io/guides/what-is-skill-md - https://www.createskills.io/guides/skill-md-template - https://www.createskills.io/sources/youtube-to-markdown - https://www.createskills.io/integrations/claude-skills --- ## Convert web pages to clean Markdown for AI - URL: https://www.createskills.io/web-to-markdown - Category: tool - Primary keyword: web to markdown - Updated: 2026-05-04 Web-to-Markdown conversion turns a readable page into structured text with headings, links, source URLs, and body content preserved for AI context. ### Sections #### What gets cleaned up createskills is built for AI context, so the capture should keep the article, docs, transcript, or post body while removing layout chrome. The goal is a file that reads like a source, not a screenshot of a website. - Keep headings, paragraphs, lists, links, and useful code snippets. - Remove repeated nav links, cookie copy, sidebars, and footer clutter. - Preserve the source URL so the context can be traced later. #### Why Markdown works well for agents Markdown gives an agent clear structure without asking it to parse HTML. Headings become sections, links stay visible, code remains copyable, and the file can live beside SKILL.md in a skill package. #### When to capture a selection For long docs pages, a selected section is often better than the whole page. Capture the API method, tutorial step, or policy clause you need, then add only that cleaned Markdown to your skill bucket. #### Reuse beyond skills You can use the Markdown directly in ChatGPT Projects, Claude Projects, Cursor context, NotebookLM, or any workflow that accepts text files. The skill zip is useful when you want the source and instructions packaged together. ### Proof and Limitations #### Index-safe sample shape The page shows a representative Markdown shape with title, source URL, sections, and preserved code blocks instead of indexing a full third-party transcript. - Useful headings remain in the exported Markdown file. - The page source keeps one canonical H1 for the page itself. - Captured source URLs stay visible for verification. #### Capture limits Output quality depends on what the current browser tab exposes. Pages with paywalls, heavy client-side rendering, or blocked text can require manual cleanup. ### Workflow Example workflow 1. Open a docs page or article that contains the source context. 2. Use the Chrome extension to capture the page or selected section. 3. Review the Markdown preview and remove anything irrelevant. 4. Download the source as a single .md file or add it to a skill bucket. ### Sample ```markdown # Server and Client Components Source: https://nextjs.org/docs/app/getting-started/server-and-client-components ## When to use a Server Component Use Server Components for data fetching, static layout, and content that does not need browser state. ## When to use a Client Component Add "use client" only when the component needs state, effects, or browser APIs. ``` ### FAQ Q: Does it keep links? A: Yes. Useful links should remain as Markdown links so you can trace claims back to the original page. Q: Does it work on signed-in pages? A: If you can read the page in your browser tab, createskills is designed to capture that visible context for your own use. Q: Is this different from saving HTML? A: Yes. HTML preserves layout and noise. Markdown is cleaner for AI tools because the content is structured as readable text. Q: Can I download one Markdown file? A: Yes. You can reuse a single cleaned source without generating a full skill zip. ### Related - https://www.createskills.io/ai-skill-generator - https://www.createskills.io/markdown-extractor-chrome-extension - https://www.createskills.io/integrations/cursor-context - https://www.createskills.io/use-cases/research-assistant-sources --- ## Turn YouTube videos into Markdown context - URL: https://www.createskills.io/sources/youtube-to-markdown - Category: source - Primary keyword: YouTube transcript to markdown - Updated: 2026-05-04 A YouTube-to-Markdown workflow captures the transcript and useful video metadata so an AI tool can reference the video as text instead of relying on memory. ### Sections #### Best use cases Video is where a lot of practical expertise lives, but it is awkward to reuse in an agent workflow. Capturing the transcript gives you durable context for creator research, technical tutorials, sales calls, interviews, lectures, and product walkthroughs. #### Combine videos into one skill One transcript is useful. A curated set is better. For example, you can capture five videos from a favorite creator and generate a hook-research skill that references the exact examples instead of asking an AI to imitate a vague style. #### Keep the source traceable Each Markdown file should include the source URL and video title. That gives you a trail back to the original clip when you need to verify a quote, rewatch a section, or remove a weak source. #### Limits to expect Transcript availability depends on the video. If a transcript is missing or incomplete, keep that limitation visible in the generated reference rather than pretending the source is complete. ### Proof and Limitations #### Before and after pattern A strong YouTube capture keeps the title, source URL, timestamped transcript excerpts, and notes that explain which sections belong in the final skill. - Keep timestamp markers when they help people verify a quote. - Remove repeated filler before generating reusable instructions. - Mark missing transcripts as a source limitation. ### Workflow Example workflow 1. Capture three tutorials about a framework or workflow. 2. Review each transcript and keep the sections that matter. 3. Generate a skill named framework-tutorial-notes. 4. Use the skill when asking an agent to apply the tutorial patterns. ### Sample ```markdown # How I use Claude Code for real engineering Source: https://youtube.com/watch?v=example ## Transcript [00:00] The first thing I do is give the agent a plan... ## Notes to use in skill - Prefer plan-first workflows for risky code changes. - Include verification commands in the final checklist. ``` ### FAQ Q: Can it capture Shorts? A: Short-form videos can be useful source material when transcript or description context is available, especially for hook and creative research. Q: Does it need my own API key? A: The createskills product handles the capture flow for supported sources. Bring-your-own API keys are not required for the normal extension workflow. Q: Can I combine multiple videos? A: Yes. Add multiple captured transcripts to one bucket, then generate a single skill package from that collection. Q: What if a transcript is unavailable? A: Use another source or attach supporting notes. A skill should be explicit about incomplete source coverage. ### Related - https://www.createskills.io/sources/instagram-reels-to-markdown - https://www.createskills.io/guides/ai-agent-skill-examples - https://www.createskills.io/ai-skill-generator - https://www.createskills.io/integrations/chatgpt-project-files --- ## Save Instagram Reels as Markdown for AI - URL: https://www.createskills.io/sources/instagram-reels-to-markdown - Category: source - Primary keyword: Instagram Reel transcript to markdown - Updated: 2026-05-04 Instagram-Reel-to-Markdown capture helps convert short-form creative references into text files that can support content strategy, hook research, and skill creation. ### Sections #### Why Reels are hard to reuse A saved Reel is easy to watch again but hard to turn into a repeatable workflow. Markdown gives you a searchable text record of the hook, structure, caption, visible claims, and source URL. #### Build a creative swipe skill Creators and marketers can collect examples around one pattern, such as objection-handling hooks, founder story videos, product demos, or educational explainers. The skill can then turn those sources into briefing context for future scripts. #### Respect source boundaries The point is to study structure and evidence, not to copy another creator. Keep source URLs attached and write the skill instructions around analysis, pattern extraction, and original output. #### Pair with other sources A Reel is stronger when combined with comments, a landing page, a YouTube transcript, or product docs. Multi-source skills help an agent understand both creative style and factual grounding. ### Workflow Example workflow 1. Capture five competitor Reels about one product category. 2. Add the cleaned source files to a short-form-hook-research bucket. 3. Generate a skill that extracts patterns without copying wording. 4. Use the skill to brief original scripts and content angles. ### Sample ```markdown # Reel: "Three mistakes founders make with demos" Source: https://instagram.com/reel/example ## Captured context Hook: "Your demo is not too long. It is too unfocused." ## Pattern notes - Opens by reframing a common complaint. - Uses three named mistakes. - Ends with a direct next action. ``` ### FAQ Q: Does it work on private Reels? A: createskills is intended for content you can legitimately access in your own browser session. Q: What content is captured? A: Capture quality depends on what is visible and available, such as captions, descriptions, transcript-like text, and source metadata. Q: Can I turn several Reels into one skill? A: Yes. That is the strongest workflow: collect related examples, then generate a skill around the pattern you want to reuse. Q: Will the skill copy another creator? A: The generated instructions should focus on analysis and original creation. Review the skill before using it. ### Related - https://www.createskills.io/guides/ai-agent-skill-examples - https://www.createskills.io/sources/reddit-thread-to-markdown - https://www.createskills.io/sources/youtube-to-markdown - https://www.createskills.io/ai-skill-generator --- ## A practical SKILL.md template for agent workflows - URL: https://www.createskills.io/guides/skill-md-template - Category: guide - Primary keyword: SKILL.md template - Updated: 2026-05-04 A good SKILL.md template names the skill, describes when to use it, lists the workflow, defines output expectations, and points to references without dumping everything into one prompt. ### Sections #### Start with a narrow trigger The description is the most important part of the file. It should say exactly when the skill helps and when it should stay out of the way. #### Keep instructions operational Write the body as steps the agent can follow. Avoid vague goals like "be strategic." Name the inputs, decision points, output format, and verification checklist. #### Reference files deliberately Use references/ for source material, examples, templates, or long notes. SKILL.md should point to those files and tell the agent when to open them. #### Test the skill against real prompts A skill is only useful if it activates for the right requests. Test it with specific prompts, vague prompts, and unrelated prompts, then tighten the description. ### Workflow Template workflow 1. Name one repeatable job the skill should perform. 2. Write a trigger description with the most important keywords first. 3. List the workflow as numbered steps. 4. Add references and examples only where they reduce ambiguity. 5. Run a real task and edit the skill based on the result. ### Sample ```markdown --- name: landing-page-review description: Use when reviewing a SaaS landing page for positioning, clarity, proof, and conversion issues. --- ## Workflow 1. Read the page copy and identify the intended buyer. 2. Compare claims against references/customer-research.md. 3. List the top conversion risks before suggesting rewrites. ## Output Return findings first, then a concise rewrite plan. ``` ### FAQ Q: What belongs in the description? A: Put the trigger use case first, then the boundaries. The description helps the agent decide whether to load the skill. Q: How long should SKILL.md be? A: Keep it as short as possible while still specifying workflow and output. Put long source material in references/. Q: Where do references go? A: Use references/ for supporting documents, examples, source captures, transcripts, PDFs, and longer notes. Q: How do I test a skill? A: Run a real task that should use it, then run one that should not. Tighten the description and workflow based on behavior. ### Related - https://www.createskills.io/guides/what-is-skill-md - https://www.createskills.io/ai-skill-generator - https://www.createskills.io/guides/ai-agent-skill-examples - https://www.createskills.io/integrations/claude-skills --- ## What is SKILL.md? - URL: https://www.createskills.io/guides/what-is-skill-md - Category: guide - Primary keyword: what is SKILL.md - Updated: 2026-05-04 SKILL.md is a Markdown file that describes a reusable agent skill: what it does, when to use it, and how to apply attached references. ### Sections #### Plain-English definition A skill is a folder of instructions and resources for a specific kind of work. SKILL.md is the required entry point. It names the skill, describes the trigger, and tells the agent what to do. #### Why Markdown Markdown is readable by people and AI tools. It keeps structure visible without locking the instructions inside a proprietary builder or chat history. #### How agents use skills Skills are meant to be loaded when relevant, not pasted into every conversation. The description helps the agent decide whether the skill applies, then the body and references guide the work. #### Why createskills exists Most people already have the knowledge they want an AI tool to use. createskills helps turn that knowledge - pages, videos, posts, PDFs, images, and notes - into clean files a skill can reference. ### Workflow Basic folder shape 1. Create a folder named for the task. 2. Add SKILL.md with metadata and instructions. 3. Add references/ for source files and examples. 4. Place the folder where your AI tool can read it or upload the files as project context. ### Sample ```text my-skill/ ├─ SKILL.md ├─ references/ │ ├─ source-notes.md │ └─ example-output.md └─ assets/ └─ template.csv ``` ### FAQ Q: Is SKILL.md only for Claude? A: Claude helped popularize the format, but the idea is useful anywhere an AI tool can read Markdown and files. Q: Is SKILL.md code? A: Usually no. It is Markdown instructions, though a skill folder can include scripts or assets when a workflow needs them. Q: Do I need one skill per task? A: Use one skill per repeatable job. Broad skills tend to trigger too often and give weaker guidance. Q: Can I version it in git? A: Yes. Because skills are plain files, teams can review, diff, and version them like other project context. ### Related - https://www.createskills.io/guides/skill-md-template - https://www.createskills.io/ai-skill-generator - https://www.createskills.io/integrations/claude-skills - https://www.createskills.io/guides/ai-agent-skill-examples --- ## AI agent skill examples you can actually copy - URL: https://www.createskills.io/guides/ai-agent-skill-examples - Category: guide - Primary keyword: AI agent skill examples - Updated: 2026-05-04 The best AI agent skill examples package one repeatable workflow with a clear trigger, concrete source files, and an output format the agent can follow. ### Sections #### Coding examples A UI review skill can include design guidelines, example components, accessibility checks, and repo conventions. A PR review skill can include review criteria, risky file patterns, and test commands. #### Marketing examples A brand voice skill can include a style guide, customer language, top-performing emails, and landing page examples. A campaign brief skill can include positioning docs and competitor pages. #### Research examples A research assistant skill can include papers, transcripts, articles, and source notes, then require the agent to separate facts, assumptions, and open questions. #### Creator examples A hook research skill can include YouTube transcripts, Reels, comments, and past scripts, then ask the agent to extract patterns before writing anything new. ### Workflow Six useful skill recipes 1. UI reviewer: design guidelines plus component examples. 2. Brand voice: style guide plus customer language. 3. Research brief: articles, PDFs, and source notes. 4. Sales objection handler: call notes plus proposal examples. 5. Creator hooks: transcripts, Reels, and comments. 6. Docs updater: product docs plus changelog entries. ### Sample ```text brand-voice-skill.zip ├─ SKILL.md └─ references/ ├─ voice-guide.md ├─ customer-reviews.md ├─ best-emails.md └─ landing-page-copy.md ``` ### FAQ Q: What makes a good skill? A: A good skill is narrow enough to trigger correctly and specific enough to change the quality of the output. Q: How many sources is enough? A: Use enough sources to ground the workflow without making the agent sort through irrelevant material. Q: Should examples be broad or narrow? A: Narrow examples usually work better. Build one skill for PR review and another for UI review instead of one generic coding skill. Q: Can I reuse one source in multiple skills? A: Yes. A product brief might belong in sales, marketing, support, and onboarding skills. ### Related - https://www.createskills.io/ai-skill-generator - https://www.createskills.io/sources/instagram-reels-to-markdown - https://www.createskills.io/sources/youtube-to-markdown - https://www.createskills.io/guides/skill-md-template --- ## Create Claude-compatible skill folders from web sources - URL: https://www.createskills.io/integrations/claude-skills - Category: integration - Primary keyword: create Claude skills - Updated: 2026-05-04 createskills helps prepare Claude-compatible skill folders by turning trusted web sources into Markdown references and bundling them with SKILL.md. ### Sections #### Claude skill structure A Claude-style skill folder centers on SKILL.md and can include supporting references, scripts, assets, or templates. createskills focuses on the source-to-reference part of that workflow. #### Progressive disclosure mindset Good skills keep the initial trigger concise and load deeper context only when needed. Put the job definition in SKILL.md and the long source material in references/. #### What createskills maps Web pages, YouTube transcripts, Instagram Reels, PDFs, images, articles, and docs can become reference files. The generated skill explains how those files should be used. #### Testing prompts After creating a skill, test it with a prompt that clearly needs the skill, a borderline prompt, and an unrelated prompt. Adjust the description until activation feels correct. ### Proof and Limitations #### Claude Skills fit The createskills output uses the same plain-file mindset: a trigger file, supporting references, and source material that can be inspected before installation. Source: [Claude Skills explained](https://claude.com/blog/skills-explained) ### Workflow Example Claude workflow 1. Capture source pages and transcripts for one recurring task. 2. Generate a skill zip from the bucket. 3. Inspect SKILL.md and the references/ folder. 4. Place or upload the files where Claude can access them. 5. Run a real task and refine the trigger description. ### Sample ```text claude-marketing-review/ ├─ SKILL.md └─ references/ ├─ brand-voice.md ├─ customer-language.md └─ campaign-examples.md ``` ### FAQ Q: Where do Claude skills go? A: The exact location depends on the Claude product and setup. The useful part is that the folder is plain files you can move or upload. Q: What files are required? A: SKILL.md is the key instruction file. Supporting references are optional but often make the skill much more useful. Q: Can I include references? A: Yes. references/ is where captured Markdown, PDFs, examples, and notes should live. Q: How do I know Claude used the skill? A: Ask for a task that clearly matches the skill and check whether the output follows the workflow and cites the provided references. ### Related - https://www.createskills.io/guides/what-is-skill-md - https://www.createskills.io/guides/skill-md-template - https://www.createskills.io/ai-skill-generator - https://www.createskills.io/sources/youtube-to-markdown --- ## Prepare clean Markdown files for ChatGPT Projects - URL: https://www.createskills.io/integrations/chatgpt-project-files - Category: integration - Primary keyword: ChatGPT project files - Updated: 2026-05-04 ChatGPT project files work best when source material is clean, scoped, and named clearly. createskills turns web sources into Markdown files that fit that workflow. ### Sections #### Project context beats repeated paste When you keep reusing the same source material, project files or knowledge files are cleaner than pasting long context into every conversation. #### Use Markdown for clarity Markdown files are easy to inspect before upload. You can keep headings, source URLs, quotes, and notes without dragging a whole web page into the project. #### Custom GPT knowledge For Custom GPTs, the same principle applies: upload well-scoped files and write short instructions that explain when the GPT should use each source. #### When to use a skill zip If your target workflow accepts a SKILL.md-style package, generate the zip. If it only accepts uploads, use the references as clean project files and adapt SKILL.md into instructions. ### Workflow Example ChatGPT workflow 1. Capture a YouTube transcript and two product pages as Markdown. 2. Review file names and delete unrelated sections. 3. Upload the Markdown files to a ChatGPT Project or Custom GPT knowledge area. 4. Use SKILL.md as the starting point for project instructions. ### Sample ```text chatgpt-project-context/ ├─ instructions-from-SKILL.md ├─ references/youtube-transcript.md ├─ references/product-page.md └─ references/customer-faq.md ``` ### FAQ Q: Can ChatGPT use Markdown files? A: Yes, Markdown is a practical format for uploaded context because it is readable and structured. Q: Is this the same as a Custom GPT? A: No. createskills prepares source files and instructions. You can use those files inside a Project or Custom GPT. Q: How many files can I upload? A: Limits vary by ChatGPT product and plan, so keep files focused and check the current upload limits in your account. Q: What should go in instructions? A: Tell ChatGPT when to reference the files, what output format to use, and how to handle missing or uncertain information. ### Related - https://www.createskills.io/web-to-markdown - https://www.createskills.io/guides/skill-md-template - https://www.createskills.io/sources/pdf-to-ai-context - https://www.createskills.io/use-cases/research-assistant-sources --- ## Bring web research into Cursor as clean context - URL: https://www.createskills.io/integrations/cursor-context - Category: integration - Primary keyword: Cursor AI context - Updated: 2026-05-04 Cursor context works better when the relevant outside knowledge is stored as readable files instead of scattered browser tabs or pasted snippets. ### Sections #### Developer research problem Most implementation tasks depend on source material outside the repo: framework docs, changelogs, GitHub issues, RFCs, blog posts, and tutorial videos. Markdown turns that research into files an AI coding tool can reference. #### Context beside code Keep captured references in a local folder when the material is safe to store with the project. For sensitive or temporary sources, keep the generated zip outside the repo and attach it only to the session. #### Rules versus references Rules tell Cursor how to behave. References give it facts and examples. A strong workflow often uses both: persistent rules for repo conventions and captured references for the specific task. #### Use exact file names in prompts After capturing sources, prompt with file names: "Use references/next-cache-docs.md and references/github-issue-412.md before changing the data loader." #### When MCP is better For a growing source library, MCP can be cleaner than manually copying files into every task. Use createskills MCP when Cursor or another agent needs to search saved captures during the work. ### Proof and Limitations #### Coding-agent evidence pattern The strongest coding captures come from official docs, changelogs, GitHub issues, and tutorial transcripts, with source titles and verification commands preserved. ### Workflow Example Cursor workflow 1. Capture framework docs, a GitHub issue, and a tutorial transcript. 2. Generate a skill package or keep the Markdown files in a task folder. 3. Ask Cursor to read the relevant references before editing code. 4. Verify the implementation against the same source files. ### Sample ```text task-context/ ├─ SKILL.md └─ references/ ├─ next-cache-docs.md ├─ github-issue-412.md └─ migration-tutorial.md ``` ### FAQ Q: Should I commit generated context? A: Commit durable team knowledge, not temporary or sensitive research. Review the files first. Q: Can this replace Cursor rules? A: No. Captured references complement rules. Use rules for stable behavior and references for task-specific context. Q: What sources work best for coding agents? A: Official docs, migration guides, GitHub issues, changelogs, architecture notes, and tested examples are usually strongest. Q: Can I use video tutorials? A: Yes. Capture the transcript as Markdown, then include only the sections relevant to the implementation. ### Related - https://www.createskills.io/web-to-markdown - https://www.createskills.io/sources/youtube-to-markdown - https://www.createskills.io/integrations/claude-code-mcp - https://www.createskills.io/markdown-extractor-chrome-extension --- ## Give your AI research assistant better sources - URL: https://www.createskills.io/use-cases/research-assistant-sources - Category: use-case - Primary keyword: AI research assistant sources - Updated: 2026-05-04 An AI research assistant is more useful when it can read the same source set you selected, with URLs, notes, and files preserved. ### Sections #### Source-backed research A good research skill includes raw sources, not only summaries. That lets the agent check claims, quote carefully, and distinguish evidence from interpretation. #### Mix source types Use articles for context, PDFs for primary documents, transcripts for talks or interviews, and your own notes for open questions. #### Ask for uncertainty The skill should instruct the agent to separate facts, assumptions, conflicts, and missing evidence. That is often more valuable than a polished summary. #### Keep research reusable A source set for one project can become the foundation for future memos, briefs, decks, or product decisions. ### Workflow Example research workflow 1. Capture five articles and two PDF reports. 2. Add a Markdown note with your research question. 3. Generate a market-research-sources skill. 4. Ask the AI assistant to synthesize findings with assumptions called out. ### Sample ```text market-research-sources.zip ├─ SKILL.md └─ references/ ├─ analyst-report.pdf ├─ founder-interview.md ├─ competitor-pages.md └─ research-questions.md ``` ### FAQ Q: Can it cite original URLs? A: Captured Markdown should preserve source URLs so you can trace important claims back to the original page. Q: How many sources should I include? A: Include enough sources to cover the question, but remove duplicates and weak references before generating the skill. Q: What makes a good research skill? A: A good research skill states the question, points to source files, and tells the agent how to handle uncertainty. Q: Can I update the source set later? A: Yes. Because the package is plain files, you can add new references and revise SKILL.md over time. ### Related - https://www.createskills.io/sources/pdf-to-ai-context - https://www.createskills.io/web-to-markdown - https://www.createskills.io/integrations/chatgpt-project-files - https://www.createskills.io/guides/skill-md-template --- ## Markdown extractor Chrome extension for AI workflows - URL: https://www.createskills.io/markdown-extractor-chrome-extension - Category: tool - Primary keyword: Markdown extractor Chrome extension - Updated: 2026-05-04 A Markdown extractor Chrome extension helps turn browser content into readable text files that AI tools can use as context. ### Sections #### Built for the browser tab you are already using createskills works from the sidepanel and capture flow so useful web context can move into your feed without copying, pasting, and cleaning text by hand. #### Capture selections, not just whole pages When only one section matters, selected capture keeps the final Markdown focused. That is especially useful for docs pages, pricing tables, API references, and long articles. #### From source to library Captured items can be previewed, edited, saved, downloaded, or added to a skill bucket. The feed becomes a working library for AI context. #### Why it is not just a clipper Traditional clippers save content for you to read later. createskills saves content so an AI workflow can read it later, with Markdown and skill packaging as first-class outputs. ### Proof and Limitations #### Browser workflow proof The extension pages emphasize selected capture, source preview, saved feed review, and export paths because those are the moments where AI-context quality is decided. - Preview before saving long captures. - Use selected capture for docs pages and API references. - Keep source URLs and cleanup notes visible. ### Workflow Example extension workflow 1. Open a useful source page. 2. Capture the page or selected section into Markdown. 3. Review the output in the feed. 4. Download the Markdown or add it to a skill bucket. 5. Generate a portable skill zip when you have enough context. ### Sample ```markdown # API rate limits Source: https://docs.stripe.com/rate-limits ## Limits Free accounts can make 60 requests per minute. ## Retry behavior Use exponential backoff after a 429 response. ``` ### FAQ Q: How is this different from a clipper? A: It is optimized for AI context: cleaned Markdown, source review, feed management, and skill packaging. Q: Does it work with selections? A: Yes. Selection capture is useful when only part of a page belongs in the final context. Q: Can I export a zip? A: Yes. Add sources to a bucket and generate a skill zip with SKILL.md and references/. Q: Can I use a single source without a skill? A: Yes. You can download or reuse a single Markdown capture directly. ### Related - https://www.createskills.io/web-to-markdown - https://www.createskills.io/ai-skill-generator - https://www.createskills.io/integrations/cursor-context - https://www.createskills.io/sources/youtube-to-markdown --- ## Turn Reddit threads into Markdown for AI research - URL: https://www.createskills.io/sources/reddit-thread-to-markdown - Category: source - Primary keyword: Reddit thread to markdown - Updated: 2026-05-19 A Reddit-thread-to-Markdown workflow captures the original post, useful comments, source URL, and cleanup notes so AI tools can analyze community evidence without relying on memory. ### Sections #### What to preserve Reddit is useful because it contains objections, workarounds, complaints, and language people use when they are not reading your marketing site. Keep the post title, subreddit, source URL, selected comments, timestamps when useful, and any moderation or deletion caveats. - Capture only the thread sections that support the research question. - Label quotes and paraphrases so the final skill does not blur evidence. - Remove voting chrome, login prompts, sidebars, and repeated recommendation blocks. #### Best AI workflows Use Reddit captures for customer-language mining, category research, objection maps, product comparison notes, and support-triage skills. The strongest outputs combine community threads with product docs and first-party customer notes. #### Limitations Reddit content is anecdotal and can be incomplete, deleted, edited, or unrepresentative. Treat it as qualitative evidence, not market truth, and keep source links attached for review. ### Proof and Limitations #### Anonymized demo shape A useful export separates post body, selected comment excerpts, theme notes, and source-traceability metadata instead of pasting the entire page shell. - Post title and subreddit stay visible. - Only selected comments enter the reusable context file. - The source URL remains attached to every capture. ### Workflow Example Reddit workflow 1. Open a relevant public Reddit thread. 2. Capture the post and useful comment sections as Markdown. 3. Delete off-topic comments and add short theme notes. 4. Add the file to a research or messaging skill bucket. ### Sample ```markdown # r/SaaS thread: Why teams churn from knowledge-base tools Source: https://www.reddit.com/r/SaaS/comments/demo/ ## Post summary The original poster describes switching tools after docs became hard to keep current. ## Selected comments - "The issue was not writing docs. It was knowing which docs were stale." - "Search got worse as the workspace grew." ## Pattern notes - Staleness and trust matter more than raw storage. ``` ### FAQ Q: Can I capture private subreddits? A: Only capture content you can legitimately access and are allowed to use in your workflow. Q: Should I keep every comment? A: No. Keep the comments that support the research question and remove noise before using the file as AI context. Q: Can Reddit threads become a skill? A: Yes. Threads work well as references inside customer-language, objection-handling, and product-research skills. ### Related - https://www.createskills.io/sources/x-thread-to-markdown - https://www.createskills.io/web-to-markdown - https://www.createskills.io/guides/ai-agent-skill-examples - https://www.createskills.io/ai-skill-generator --- ## Save X threads as Markdown for AI context - URL: https://www.createskills.io/sources/x-thread-to-markdown - Category: source - Primary keyword: X thread to markdown - Updated: 2026-05-19 X-thread-to-Markdown capture converts a thread or post into structured text that an AI tool can quote, compare, summarize, or use as source context. ### Sections #### Why threads need structure Social threads mix the actual argument with replies, promoted content, login prompts, media cards, and recommendation UI. A clean Markdown capture should preserve the thread sequence and source URL while removing interface noise. #### Use cases X captures are useful for trend monitoring, founder posts, analyst threads, launch notes, design references, and content swipe files. Add source notes before turning them into reusable instructions. #### Verification Social posts can change or disappear. Keep the source URL, author handle, and capture date so a human can verify claims before publishing or shipping analysis. ### Proof and Limitations #### Source traceability The sample pattern keeps author, date, URL, thread body, and extracted claims separate so downstream AI answers can distinguish evidence from interpretation. ### Workflow Example X workflow 1. Capture a public thread or post from the browser. 2. Review the Markdown order and remove unrelated replies. 3. Add claim notes or media descriptions if they matter. 4. Use the file in a swipe, research, or trend-monitoring skill. ### Sample ```markdown # X thread: Launch notes for an AI workflow tool Source: https://x.com/founder/status/demo Author: @founder Captured: 2026-05-19 ## Thread 1. We rebuilt onboarding around one setup checklist. 2. The biggest drop-off was connecting source context. ## Claim notes - Setup friction is the main conversion risk. ``` ### FAQ Q: Does this capture replies? A: Capture quality depends on what is visible in the browser. Keep replies only when they add useful evidence. Q: Can I use it for swipe files? A: Yes, but write instructions around pattern analysis and original work instead of copying another author. Q: Why use Markdown instead of screenshots? A: Markdown is searchable, diffable, and easier for AI tools to reference than image-only screenshots. ### Related - https://www.createskills.io/sources/reddit-thread-to-markdown - https://www.createskills.io/sources/youtube-to-markdown - https://www.createskills.io/markdown-extractor-chrome-extension - https://www.createskills.io/ai-skill-generator --- ## Turn PDFs into AI context without losing the source - URL: https://www.createskills.io/sources/pdf-to-ai-context - Category: source - Primary keyword: PDF to AI context - Updated: 2026-05-19 PDF-to-AI-context workflows work best when the original PDF stays attached and a Markdown note explains the source, key pages, limits, and intended use. ### Sections #### Do not flatten everything blindly Some PDFs contain tables, charts, footnotes, legal language, or visual context that should remain available as the original file. A Markdown companion note helps the agent start in the right place while keeping the source inspectable. #### What the note should include Include document title, source URL or origin, capture date, page ranges, summary, key excerpts, and uncertainty notes. If the PDF is scanned or image-heavy, label that limitation explicitly. #### Good fits PDF context is useful for research papers, analyst reports, onboarding manuals, sales briefs, policy documents, and exported decks that need to stay close to the original source. ### Proof and Limitations #### Traceability first The recommended package keeps the PDF and Markdown side by side so an agent can use the summary without losing the original document boundary. - Keep page references for claims and quotes. - Mark scanned, partial, or manually summarized files. - Review sensitive documents before upload. ### Workflow Example PDF workflow 1. Upload or attach the PDF as a source reference. 2. Create a Markdown companion note with pages, summary, and limits. 3. Combine the PDF note with supporting web captures. 4. Generate a research or sales-enablement skill package. ### Sample ```text market-report-context/ ├─ SKILL.md └─ references/ ├─ market-report.pdf ├─ market-report-notes.md └─ supporting-articles.md ``` ### FAQ Q: Should I convert the whole PDF to Markdown? A: Only when the text converts cleanly. For complex documents, keep the PDF and add a Markdown guide to the important pages. Q: Can AI tools read the original PDF? A: Many can, but limits vary. The Markdown note gives the workflow a stable summary and source map. Q: Can this become a SKILL.md package? A: Yes. Put the PDF and companion notes in references/ and explain the review workflow in SKILL.md. ### Related - https://www.createskills.io/use-cases/research-assistant-sources - https://www.createskills.io/integrations/chatgpt-project-files - https://www.createskills.io/guides/skill-md-template - https://www.createskills.io/web-to-markdown --- ## Connect Claude Code to your createskills MCP server - URL: https://www.createskills.io/integrations/claude-code-mcp - Category: integration - Primary keyword: Claude Code MCP server - Updated: 2026-05-19 The createskills MCP setup connects Claude Code to saved Markdown sources so the agent can search, read, capture, and reuse source context without manual copy-paste. ### Sections #### What the MCP connection adds Claude Code can work from your local files and repo context. The createskills MCP server adds a hosted source library: saved web pages, transcripts, posts, PDFs, and generated Markdown that the agent can retrieve when a task needs outside evidence. #### Public setup path This public page explains the workflow before sign-in. The account setup page holds the private endpoint, authentication details, and connection values for your createskills account. #### Best prompts Ask Claude Code to search your source library before changing implementation details, summarizing market research, or writing source-backed docs. Name the source category when you can. ### Proof and Limitations #### Available MCP tasks The hosted setup is designed around searching saved sources, reading full Markdown, capturing public URLs, organizing context, and transforming Markdown for a task. - Use account setup for private connection values. - Use public pages to understand the workflow before sign-in. - Keep source URLs attached for later verification. ### Workflow Claude Code setup flow 1. Install the Chrome extension and capture a few useful sources. 2. Create or sign in to your createskills account. 3. Open the private agent-connection setup page for your MCP values. 4. Add the MCP server to Claude Code. 5. Ask Claude Code to search saved sources before a source-backed task. ### Sample ```text Use the createskills MCP source library before editing. Find saved sources about Next.js caching and summarize the constraints. Then update the implementation and cite the source files you used. ``` ### FAQ Q: Is the MCP endpoint public? A: The explanatory page is public. Private connection values and authentication live behind account setup. Q: Does Claude Code need the Chrome extension? A: The extension is the easiest way to capture sources, while MCP is how the agent retrieves them later. Q: Can Claude Code capture new URLs through MCP? A: The workflow is designed to support public URL capture where the server can access the page. ### Related - https://www.createskills.io/integrations/codex-mcp - https://www.createskills.io/integrations/cursor-context - https://www.createskills.io/compare/claude-skills-vs-mcp - https://www.createskills.io/ai-skill-generator --- ## Use createskills MCP with Codex workflows - URL: https://www.createskills.io/integrations/codex-mcp - Category: integration - Primary keyword: Codex MCP server - Updated: 2026-05-19 Codex MCP setup lets a coding agent search and read createskills source captures during implementation, documentation, and research tasks. ### Sections #### Why Codex needs source context Codebase context is not always enough. Product docs, framework migration guides, support notes, design references, and research threads often explain the change better than the repository alone. #### MCP versus pasted files Pasted files work for one-off tasks. MCP is better when the agent needs to search a growing source library or retrieve the right capture while work is underway. #### Human review still matters Use MCP retrieval as evidence gathering, not blind authority. Ask the agent to name source files it used and run the normal repo verification commands. ### Proof and Limitations #### Agent-friendly retrieval The setup is optimized for a small set of source actions: search, read, capture public URLs, organize, and transform Markdown into task-specific context. ### Workflow Codex MCP workflow 1. Capture docs, issues, or transcripts with createskills. 2. Connect the hosted MCP server in your Codex-compatible environment. 3. Ask the agent to search sources before making a change. 4. Review both the code diff and the sources the agent referenced. ### Sample ```text Before editing, search createskills for "billing migration notes". Use the relevant captures to update the checkout docs. List source titles and verification commands in the final response. ``` ### FAQ Q: Can Codex use web captures directly? A: With MCP connected, the agent can retrieve saved captures that createskills has stored as Markdown. Q: Should I still include repo files? A: Yes. MCP source context complements repository search; it does not replace reading the codebase. Q: What sources are best for coding tasks? A: Official docs, changelogs, migration guides, product specs, GitHub issues, and tutorial transcripts usually work best. ### Related - https://www.createskills.io/integrations/claude-code-mcp - https://www.createskills.io/integrations/cursor-context - https://www.createskills.io/web-to-markdown - https://www.createskills.io/compare/claude-skills-vs-mcp --- ## Claude Skills vs MCP: when to use each - URL: https://www.createskills.io/compare/claude-skills-vs-mcp - Category: comparison - Primary keyword: Claude Skills vs MCP - Updated: 2026-05-19 Use Claude Skills for repeatable workflows and file-based instructions; use MCP when an agent needs to query tools, data, or saved sources during work. Many serious agent setups need both. ### Sections #### The practical distinction A Skill is a packaged capability. MCP is a connection layer. If the job is "review landing pages in our house style," a skill can hold the workflow. If the job is "find the latest saved customer calls and use them," MCP is the retrieval path. #### Use both when context changes Static instructions belong in SKILL.md. Changing source material belongs in a library or tool the agent can query. createskills supports both: source-backed skill folders and a hosted MCP source library. #### Security model Skills are easiest to inspect when they are plain Markdown and references. MCP needs tighter permission thinking because it can expose live tools or account data. Keep both scoped to the work they should influence. ### Comparison Table Columns: Criteria | Claude Skills | MCP - Best job: Reusable workflow instructions, examples, and reference folders. / Runtime access to tools, data, APIs, and hosted source libraries. - Context shape: Plain files such as SKILL.md, references/, scripts/, and assets/. / Server-exposed tools and resources the agent can call when needed. - Setup burden: Mostly file authoring and placement in the target agent environment. / Requires server configuration, auth, transport, and tool permissions. - Risk: Poor triggers or unsafe bundled scripts can steer work incorrectly. / Overbroad tools or credentials can expose data and actions. - Where createskills fits: Generates source-backed SKILL.md packages and references. / Exposes saved captures through hosted source-library retrieval. Skills and MCP solve different parts of agent context. Skills tell the agent how to work; MCP lets the agent retrieve or act on the right context while working. ### Proof and Limitations #### First-party implementation stance createskills treats skills as transparent files and MCP as a retrieval channel for saved sources, not as interchangeable labels. Source: [Claude Skills explained](https://claude.com/blog/skills-explained) ### Workflow Decision workflow 1. Write the reusable instructions as a skill when the workflow repeats. 2. Put long or changing source material in references or a source library. 3. Use MCP when the agent needs to search or fetch sources during the task. 4. Ask the agent to name the skill and sources it used. ### Sample ```text Use a Skill when the agent needs a repeatable operating procedure. Use MCP when the agent needs runtime access to saved sources or tools. Use both when the procedure is stable but the source library changes. ``` ### FAQ Q: Is MCP a replacement for Claude Skills? A: No. MCP connects tools and data. Skills package task instructions and references. They are complementary. Q: Which should I implement first? A: Start with the bottleneck. If instructions are inconsistent, build a skill. If source retrieval is painful, connect MCP. Q: Can createskills generate both? A: createskills can prepare source-backed skill packages and expose saved captures through its hosted MCP server. ### Related - https://www.createskills.io/integrations/claude-skills - https://www.createskills.io/integrations/claude-code-mcp - https://www.createskills.io/integrations/codex-mcp - https://www.createskills.io/guides/what-is-skill-md --- ## ChatGPT Projects vs Claude Skills for reusable context - URL: https://www.createskills.io/compare/chatgpt-projects-vs-claude-skills - Category: comparison - Primary keyword: ChatGPT Projects vs Claude Skills - Updated: 2026-05-19 ChatGPT Projects are strong for persistent chat context and uploaded files; Claude Skills are stronger as portable, named workflow folders with SKILL.md and references. ### Sections #### Where createskills fits createskills produces clean Markdown references that can be uploaded to ChatGPT Projects or placed inside a skill folder. The same source capture should not be trapped in one product if the team needs reuse across tools. #### Choose by workflow Use a project when the work lives in one ongoing chat space. Use a skill when the workflow needs a named trigger, repeated procedure, or file package that can move between environments. #### Keep instructions concise In either model, long source material belongs in files. The instructions should explain when to use the files, how to cite uncertainty, and what output format to return. ### Comparison Table Columns: Criteria | ChatGPT Projects | Claude Skills - Primary shape: Project instructions plus uploaded files inside ChatGPT. / A portable folder with SKILL.md and optional references, scripts, and assets. - Portability: Useful inside the project environment. / Plain files can be reviewed, versioned, moved, or adapted. - Activation: The project context is available inside that project. / The skill description helps the agent decide when to load it. - Best fit: Ongoing chats, knowledge work, and Custom GPT-style uploads. / Repeatable agent workflows with named operating procedures. Both approaches improve context reuse. The main decision is whether you need a chat workspace or a portable workflow package. ### Proof and Limitations #### Shared source strategy The same captured Markdown can support both setups: upload it as project files or include it under references/ with SKILL.md. ### Workflow Reuse workflow 1. Capture source pages or transcripts as Markdown. 2. Upload files to a ChatGPT Project for ongoing chat work. 3. Package the same files into a skill when the workflow repeats. 4. Keep source URLs in both places for verification. ### Sample ```text source-context/ ├─ project-instructions.md ├─ SKILL.md └─ references/ ├─ customer-language.md └─ product-docs.md ``` ### FAQ Q: Can I use the same Markdown in both tools? A: Yes. That is the point of keeping source captures as normal files. Q: Which is better for teams? A: Teams often prefer portable files because they can review, version, and adapt them across tools. Q: Do I need a skill for every project? A: No. Use skills for repeated workflows, not one-off chats. ### Related - https://www.createskills.io/integrations/chatgpt-project-files - https://www.createskills.io/integrations/claude-skills - https://www.createskills.io/guides/skill-md-template - https://www.createskills.io/ai-skill-generator --- ## SKILL.md vs CLAUDE.md: what belongs where - URL: https://www.createskills.io/compare/skill-md-vs-claude-md - Category: comparison - Primary keyword: SKILL.md vs CLAUDE.md - Updated: 2026-05-19 Use CLAUDE.md for project-wide behavior and repo conventions; use SKILL.md for a reusable task-specific workflow with optional references. ### Sections #### Project rules are ambient CLAUDE.md is useful for commands, architecture notes, testing expectations, and stable project constraints. It should help the agent work in the repo without overwhelming every task. #### Skills are selective A SKILL.md should describe one job clearly enough that an agent can decide when it applies. Put long examples and sources in references/ so the skill can load them only when useful. #### Where source captures go Captured web pages, transcripts, PDFs, and social posts usually do not belong inline in either file. Store them as references and point to them from the relevant instruction file. ### Comparison Table Columns: Criteria | SKILL.md | CLAUDE.md - Scope: One reusable capability or workflow. / Project-wide instructions and repo conventions. - When loaded: When the agent decides the skill is relevant. / As ambient project guidance in Claude-oriented coding workflows. - Source material: Long examples and references can live beside the file. / Should point to canonical docs instead of copying long references. - Common mistake: Making one broad skill that triggers too often. / Turning the project instruction file into a huge knowledge dump. Keep stable project behavior in CLAUDE.md and reusable task workflows in SKILL.md. Long source material should live in referenced files. ### Proof and Limitations #### Maintainability rule If a paragraph applies to every task in the repo, it is probably project guidance. If it applies only to a repeatable job, it is probably skill guidance. ### Workflow Placement workflow 1. Write project-wide commands and conventions in CLAUDE.md. 2. Create a SKILL.md for each repeated workflow. 3. Move long examples and sources into references/. 4. Test whether the skill triggers only for relevant prompts. ### Sample ```text CLAUDE.md: build commands, repo conventions, review rules. SKILL.md: landing-page-review workflow. references/: customer language, examples, checklist. ``` ### FAQ Q: Can a repo have both? A: Yes. Use CLAUDE.md for the repo and SKILL.md files for specific capabilities. Q: Should I put source transcripts in CLAUDE.md? A: No. Keep long source material in referenced files so it does not pollute every task. Q: How narrow should a skill be? A: Narrow enough that it has a clear trigger and output shape. ### Related - https://www.createskills.io/guides/what-is-skill-md - https://www.createskills.io/guides/skill-md-template - https://www.createskills.io/integrations/claude-skills - https://www.createskills.io/compare/claude-skills-vs-mcp --- ## createskills vs web2md-style converters - URL: https://www.createskills.io/compare/createskills-vs-web2md - Category: comparison - Primary keyword: createskills vs web2md - Updated: 2026-05-19 Use a basic web2md converter for one-off Markdown extraction; use createskills when you need source review, saved captures, skill packages, and MCP access for agents. ### Sections #### One-off conversion versus context system A one-page converter is enough when you just need Markdown once. The createskills workflow matters when those captures become a reusable source set for ChatGPT, Claude, Cursor, Codex, or skill folders. #### Why saved sources matter AI workflows improve when sources can be searched, reviewed, cleaned, grouped, and retrieved later. That is why createskills adds the feed, source library, transformations, and hosted MCP server. #### When a converter is still fine If you only need a quick Markdown copy of a public article, a basic converter can be enough. If you need source provenance, multi-source workflows, or agent access, use a source library. ### Comparison Table Columns: Criteria | createskills | web2md-style converter - Primary job: Capture, save, organize, transform, and reuse sources for AI workflows. / Convert a web page to Markdown. - Source library: Feed, folders, saved captures, and MCP retrieval. / Often download or copy output only. - Skill packaging: Can package SKILL.md with references for repeatable work. / Usually outside the scope of a converter. - Best fit: AI builders, creators, researchers, and teams reusing many sources. / Fast one-off extraction when no library is needed. The difference is workflow depth. createskills is optimized for turning many sources into reusable agent context, not only converting one page. ### Proof and Limitations #### No overclaim This comparison does not claim createskills replaces every converter. It explains when the extra workflow layer is worth the added setup. ### Workflow Selection workflow 1. Use a simple converter for a single disposable capture. 2. Use createskills when the source should be saved, cleaned, or reused. 3. Group related sources into a bucket when the workflow repeats. 4. Connect MCP when agents need runtime source retrieval. ### Sample ```text One page to paste now: basic converter. Many sources for future AI work: createskills feed. Repeatable workflow: SKILL.md package. Agent retrieval during work: createskills MCP. ``` ### FAQ Q: Is createskills just a web-to-Markdown converter? A: No. Conversion is one part of the workflow. The product also saves sources, supports transformations, prepares skill packages, and exposes saved context through MCP. Q: When is web2md enough? A: When you only need a quick one-off Markdown extract and do not need a source library. Q: Can I download a single Markdown file in createskills? A: Yes. You can use a single capture without generating a full skill. ### Related - https://www.createskills.io/web-to-markdown - https://www.createskills.io/markdown-extractor-chrome-extension - https://www.createskills.io/ai-skill-generator - https://www.createskills.io/integrations/claude-code-mcp # Kit Previews ## Generate Viral Hooks - URL: https://www.createskills.io/kits/generate-viral-hooks - Status: Coming soon - Price label: $19 one-time - Audience: Creators, founders, marketers, and operators who need more compelling openings for videos, posts, emails, and landing pages. - Sources: 24 A hook-writing kit built around proven attention patterns, retention logic, and concrete examples instead of generic prompt formulas. - Outcome: Turn rough ideas into sharper short-form hooks, title angles, cold opens, and first-line variations. ### Included Sources - Short-form hook pattern notes (example): Manually extracted from creator examples and editorial teardowns. - Retention and curiosity research (article): Cleaned notes from public creator strategy essays and video analysis. - YouTube and TikTok opening examples (video): Source-backed examples with context on why each opening works. - Copywriting frameworks for first lines (book): Summarized from classic direct-response and modern creator sources. ### Preview Instruction Use this kit when the first sentence matters. The agent should identify the promise, tension, audience pain, and proof before writing variations. Strong hooks should feel specific enough to be useful, not broad enough to be safe. ### Trust Notes - Sources are curated and cleaned by hand, with labels that keep examples separate from opinion. - The kit is designed for ideation and editing; you should still review claims and platform-specific advice. - The paid artifact is not available yet, so this public page is a transparent preview. --- ## Startup Advisor - URL: https://www.createskills.io/kits/startup-advisor - Status: Coming soon - Price label: $19 one-time - Audience: Early-stage founders, indie hackers, product builders, and operators deciding what to build, sell, or cut. - Sources: 31 A founder-advisor kit that turns startup essays, tactical interviews, and operating principles into a practical decision partner. - Outcome: Stress-test startup ideas, positioning, growth loops, product strategy, and founder tradeoffs with stronger context. ### Included Sources - Early-stage strategy essays (article): Public essays and talks converted into structured operating notes. - Founder interview excerpts (interview): Curated quotes and examples from public founder interviews. - Product-market fit and default-alive notes (article): Clean summaries of widely cited startup frameworks. - Positioning and customer discovery prompts (example): Synthesized from public customer research and sales discovery examples. ### Preview Instruction Use this kit when you need a second brain that pushes past founder optimism. The agent should ask what would have to be true, what evidence exists, and which next action reduces the most uncertainty. ### Trust Notes - The kit separates tactical examples from general startup doctrine so advice stays grounded. - It is not legal, financial, or investment advice; it is a structured thinking aid. - The current page previews scope while entitlement-backed artifacts are prepared. --- ## Grow on YouTube - URL: https://www.createskills.io/kits/grow-on-youtube - Status: Coming soon - Price label: $19 one-time - Audience: Long-form creators, solo founders, educators, and media operators building a durable YouTube channel. - Sources: 28 A YouTube growth kit that helps agents reason from topic-market fit, retention, packaging, and creator examples. - Outcome: Plan stronger YouTube topics, titles, thumbnails, retention structures, and channel experiments. ### Included Sources - Creator strategy breakdowns (video): Manually cleaned notes from public YouTube strategy videos and transcripts. - Title and thumbnail pattern library (example): Examples grouped by promise, stakes, contrast, and audience maturity. - Retention and structure research (article): Public analysis converted into concise planning references. - Channel positioning notes (interview): Public creator interviews distilled into tactical guidance. ### Preview Instruction Use this kit when a video idea needs to survive before production starts. The agent should test who wants the video, why now, what the title promises, and whether the structure keeps delivering on that promise. ### Trust Notes - Examples are included for pattern recognition, not copying. - Advice is tuned for thoughtful channel growth, not spam automation. - The paid file bundle is still being finalized before checkout is enabled. --- ## TikTok Growth Hacker - URL: https://www.createskills.io/kits/tiktok-growth-hacker - Status: Coming soon - Price label: $19 one-time - Audience: Short-form creators, social teams, indie founders, and agencies running frequent content tests. - Sources: 26 A short-form growth kit for turning messy ideas into repeatable formats, testable hypotheses, and practical publishing systems. - Outcome: Build repeatable TikTok and short-form experiments from hooks, formats, trends, scripts, and iteration loops. ### Included Sources - TikTok format and hook examples (social): Public examples summarized into reusable pattern notes. - Creator operations playbooks (newsletter): Curated public writing about volume, iteration, and production systems. - Algorithm and retention analysis (article): Public platform and creator strategy sources distilled into guidance. - Faceless content and template notes (reddit): Public discussion threads summarized with source context preserved. ### Preview Instruction Use this kit when you need a system, not a single clever post. The agent should generate ideas as experiments with a clear format, audience signal, hook, expected behavior, and learning goal. ### Trust Notes - The kit avoids claims of guaranteed virality and treats growth as experimentation. - Sources are labeled so platform folklore does not masquerade as fact. - Artifacts remain gated until the first purchase-ready release is complete. --- ## High Conversion Copywriter - URL: https://www.createskills.io/kits/high-conversion-copywriter - Status: Coming soon - Price label: $19 one-time - Audience: Founders, marketers, product teams, and agencies improving conversion on pages and funnels. - Sources: 29 A conversion copy kit built around voice-of-customer research, offer clarity, proof, objections, and page structure. - Outcome: Write and critique landing pages, offers, emails, and conversion copy with better customer and proof context. ### Included Sources - Voice-of-customer extraction notes (example): Examples and rubrics for turning research into copy inputs. - Landing-page structure references (article): Public teardown and copywriting references converted to Markdown notes. - Offer and objection frameworks (book): Summaries of classic direct-response and modern SaaS copy frameworks. - Proof, guarantee, and CTA examples (example): Annotated examples from public landing pages and launch materials. ### Preview Instruction Use this kit when copy needs to make a buyer feel understood. The agent should start from audience language, clarify the promise, map proof to objections, and make each section earn its place. ### Trust Notes - The kit prioritizes truthful, evidence-backed copy over manipulative pressure. - Examples are included as references, not swipe files for direct copying. - Checkout and private downloads are intentionally disabled until artifacts are ready.