Loading...
Loading...
Found 1,051 Skills
Preview Markdown, LaTeX, PDF, or code artifacts in the browser or as PDF. Use when the user wants to review a written artifact, export a report, or view a rendered document.
Convert the current plan, code review, or structured content in context into a persistent markdown checklist file under .claude/plans/
Render a markdown draft / any document in the conversation context into a single-file "paper proposal" HTML — serif body, monospace meta, numbered sections, inline SVG figures, callouts, tables, optional interactive elements. Trigger when the user says "turn this into HTML / render as a web page / make a pretty HTML / give me a single-page doc / generate article HTML / paper-style HTML / convert to article html / render this as a doc html" or similar, and wants a **static single file** rather than Figma/PDF/PPT. Also fires when the user pastes some markdown and says "beautify this / typeset this / give me a web version". Do NOT trigger when the user wants slides, needs a backend, or needs a multi-page site.
Generate and publish blog posts from any project to kelegele/agent-blog. ZERO DEPENDENCIES — does NOT require Node.js, pnpm, git, or any local build tools. Works with only a browser and a GitHub token. Triggers on: "写篇博客", "blog this", "发博文", "publish blog", "把项目写成文章", "写篇文章", "blog it", "post article", "新文章", "new blog post", "blog this project", "发一篇博文", "写一篇博文", "blog post about this", "edit blog post", "修改文章", "更新博文", "edit article". Collects project context, collaborates on outline, writes Markdown with correct frontmatter, validates article format, generates a standalone HTML preview by reading live blog source, manages draft/review/publish flow. Pushes to kelegele/agent-blog main branch. Vercel auto-deploys on push. Use this skill whenever the user expresses intent to write about their current work as a blog post.
Set up a Markdown-based local ticket management system for your project. Create task, bug, and chapter tickets in the .local/ticket/ directory, and track progress using checklists. It can be used casually since it is not managed by Git. Language and framework agnostic. Use when requested: "introduce ticket system", "task management with Markdown", "set up local ticket management", "create ticket", "create bug ticket", "create chapter", "create epic", "local ticket system", "setup ticket management".
Use when converting PDFs, DOCX, HTML, scanned papers, reports, proposals, tables, or figures into Markdown, text, extracted assets, or quality reports for an academic research repository.
Karpathy's LLM Wiki: build/query interlinked markdown KB.
Converting markdown plans into beads (tasks with dependencies) and polishing them until they're implementation-ready. The bridge between planning and agent swarm execution. Includes exact prompts used.
Validate markdown link portability in skills. TRIGGERS - check links, validate portability, fix broken links, relative paths.
Fetch and extract content from web pages, converting HTML to clean markdown. Use when users want to read web articles, extract information from URLs, scrape web content, or when the built-in WebFetch tool fails due to network restrictions. Trigger when user provides URLs to read, asks to fetch web content, or needs to extract text from websites.
Use when needing to scrape documentation websites into markdown for AI context. Triggers on "scrape docs", "download documentation", "get docs for [library]", or creating local copies of online documentation. CRITICAL - always analyze sitemap first before scraping.
Import markdown documents and mermaid diagrams into Joplin using the Joplin CLI.