agentsclimarketplace

Docs & writing

16,633 rows, by stacks then stars

3,030 of these skill files have been read, by 1,951 distinct authors, and what they tell an agent counted. What Docs & writing authors agree on, and what they forbid

  • Test driven development

    pantheon-org/tekhne/skills/testing/test-driven-development Skill

    10★ repo

    Guides TDD (test-driven development) with red-green-refactor workflows, test-first feature delivery, bug reproduction through failing tests, behavior-focused assertions, and refactoring safety. Use when writing unit tests, implementing new functions, adding test coverage, fixing regressions, changing APIs, or restructuring code under test — especially when a user says "write tests first", "TDD", or "test before code".

  • Documentation writer

    a-tokyo/agent-skills-harness/.agents/skills/documentation-writer Skill

    10★ repo

    Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.

    The same file is in 7 other repositories

  • Writing great skills

    a-tokyo/agent-skills-harness/.agents/skills/writing-great-skills Skill

    10★ repo

    Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

    The same file is in 6 other repositories

  • Api documentation

    autohandai/community-skills/api-documentation Skill

    10★ repo

    Create comprehensive API documentation for developers. Use when documenting REST APIs, GraphQL schemas, or SDK methods. Handles OpenAPI/Swagger, interactive docs, examples, and API reference guides.

    The same file is in 4 other repositories

  • Building phishing reporting button workflow

    autohandai/community-skills/building-phishing-reporting-button-workflow Skill

    10★ repo

    Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.

  • Changelog maintenance

    autohandai/community-skills/changelog-maintenance Skill

    10★ repo

    Maintain a clear and informative changelog for software releases. Use when documenting version changes, tracking features, or communicating updates to users. Handles semantic versioning, changelog formats, and release notes.

    The same file is in 3 other repositories

  • Content strategy

    autohandai/community-skills/content-strategy Skill

    10★ repo

    When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.

    The same file is in 1 other repository

  • Context7

    autohandai/community-skills/context7 Skill

    10★ repo

    Fetch up-to-date library documentation via Context7 API. Use PROACTIVELY when: (1) Working with ANY external library (React, Next.js, Supabase, etc.) (2) User asks about library APIs, patterns, or best practices (3) Implementing features that rely on third-party packages (4) Debugging library-specific issues (5) Need current documentation beyond training data cutoff (6) AND MOST IMPORTANTLY, when you are installing dependencies, libraries, or frameworks you should ALWAYS check the docs to see what the latest versions are. Do not rely on outdated knowledge. Always prefer this over guessing library APIs or using outdated knowledge.

    The same file is in 3 other repositories

  • Copywriting

    autohandai/community-skills/copywriting Skill

    10★ repo

    When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.

    The same file is in 5 other repositories

  • Doc coauthoring

    autohandai/community-skills/doc-coauthoring Skill

    10★ repo

    Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

    The same file is in 39 other repositories

  • Document writer

    autohandai/community-skills/document-writer Skill

    10★ repo

    Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

  • Documentation writing

    autohandai/community-skills/documentation-writing Skill

    10★ repo

    Technical documentation best practices and API documentation

  • Docx

    autohandai/community-skills/docx Skill

    10★ repo

    Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

    The same file is in 31 other repositories

  • Generating threat intelligence reports

    autohandai/community-skills/generating-threat-intelligence-reports Skill

    10★ repo

    Generates structured cyber threat intelligence reports at strategic, operational, and tactical levels tailored to specific audiences including executives, security operations teams, and technical analysts. Use when producing finished intelligence products from raw collection data, creating sector threat briefings, or delivering post-incident intelligence assessments. Activates for requests involving CTI report writing, threat briefings, intelligence products, finished intelligence, or executive security reporting.

    The same file is in 1 other repository

  • Markdown url

    autohandai/community-skills/markdown-url Skill

    10★ repo

    Route any website you need to visit through markdown.new by prefixing the URL. **WHEN TO USE:** - You would normally open a website link to read content (docs, blog posts, changelogs, GitHub issues, etc.) - You need a cleaner, Markdown-friendly view for copying notes or summarizing

    The same file is in 3 other repositories

  • Nvidia nemo gym docs

    autohandai/community-skills/nvidia-nemo-gym-docs Skill

    10★ repo

    'Maintain the NeMo Gym Fern docs site — add, update, move, or remove pages under fern/. Use for any documentation change. Triggered by: "edit docs", "add doc page", "update docs", "rename page", "fix broken link", "add redirect", "preview docs", "publish docs", any request that touches `fern/`.

  • Nvidia nemo rl docs

    autohandai/community-skills/nvidia-nemo-rl-docs Skill

    10★ repo

    Documentation conventions for NeMo-RL. Covers docs/index.md updates and docstring format.

  • Nvidia nemoclaw contributor update docs

    autohandai/community-skills/nvidia-nemoclaw-contributor-update-docs Skill

    10★ repo

    Scan recent git commits for changes that affect user-facing behavior, then draft or update the corresponding documentation pages and refresh generated user skills for release prep. Use when docs have fallen behind code changes, after a batch of features lands, during daily release prep, or when preparing a release. Trigger keywords - update docs, draft docs, docs from commits, sync docs, catch up docs, doc debt, docs behind, docs drift, release prep docs, refresh user skills.

  • Nvidia nemoclaw user overview

    autohandai/community-skills/nvidia-nemoclaw-user-overview Skill

    10★ repo

    Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Trigger keywords - nemoclaw ecosystem, openclaw openshell, nemoclaw vs openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw overview, openclaw always-on assistants, nvidia openshell, nvidia nemotron, nemoclaw release notes, nemoclaw changelog.

  • Nvidia tensorrt llm kernel cute writing

    autohandai/community-skills/nvidia-tensorrt-llm-kernel-cute-writing Skill

    10★ repo

    'Write and implement GPU kernels using NVIDIA CuTe DSL (CUTLASS 4.x Python API) — NOT for Triton, CUDA C++, or conceptual explanations. Trigger only when the user wants to write or implement a kernel, not when asking questions about CuTe DSL concepts or layouts. CuTe DSL uses cute.jit/cute.kernel decorators and cutlass.cute imports. Covers element-wise kernels, GEMM patterns, reductions, memory hierarchy (global/shared/register/TMA), MMA tensor core operations, software pipelining, and framework integration.

  • Nvidia tensorrt llm kernel triton writing

    autohandai/community-skills/nvidia-tensorrt-llm-kernel-triton-writing Skill

    10★ repo

    'ONLY for OpenAI Triton (@triton.jit) kernel development. NEVER use for CUDA C++ kernels, TileIR, or profiling tools (ncu, nsys). The user''s request must involve Triton explicitly. Covers Triton-specific patterns: fused elementwise, reductions (softmax, LayerNorm, RMSNorm), tiled GEMM with triton.autotune, and flash attention. Workflow: design, write, verify (with fast-path for explicit requests).

  • Nvidia tensorrt llm perf nsight compute analysis

    autohandai/community-skills/nvidia-tensorrt-llm-perf-nsight-compute-analysis Skill

    10★ repo

    'Analyze ncu (NVIDIA Nsight Compute) profiling output: SOL% bottleneck classification, roofline analysis, occupancy diagnosis, memory hierarchy analysis, warp stall analysis, metric interpretation, and programmatic .ncu-rep report analysis. NOT for kernel writing or code generation, Nsight Systems (nsys), host-side profiling, or system-level profiling.

  • Nvidia tensorrt llm perf workload profiling

    autohandai/community-skills/nvidia-tensorrt-llm-perf-workload-profiling Skill

    10★ repo

    'Code instrumentation for timing workloads. Two scenarios: (1) Training loop — inject manual timing to report per-iteration latency, throughput (samples/sec), and data load time. (2) Standalone kernel/op — write CUDA event timing code with warmup, per-iteration statistics, and anti-pattern avoidance. Also covers NVTX annotation for labeling profiler timelines. NOT for: running or analyzing profiler tools (nsys, ncu, Nsight Systems, Nsight Compute), writing kernels (Triton, CuTe, CUDA), applying optimizations (CUDA Graphs, gradient checkpointing, fusion), or interpreting roofline/SOL% metrics. Triggers: "measure throughput", "benchmark this function", "time my training loop", "samples per second", "NVTX annotate", "instrument my dataloader", "data load time", "kernel timing", "how do I time".

  • Nvidia video search and summarization report

    autohandai/community-skills/nvidia-video-search-and-summarization-report Skill

    10★ repo

    Produce video analysis reports by discovering the deployed VSS agent, querying POST /generate for a timestamped captioned summary of the clip, then formatting the agent reply as the standard Video Analysis Report markdown.

  • Openai docs skill

    autohandai/community-skills/openai-docs-skill Skill

    10★ repo

    Query the OpenAI developer documentation via the OpenAI Docs MCP server using CLI (curl/jq). Use whenever a task involves the OpenAI API (Responses, Chat Completions, Realtime, etc.), OpenAI SDKs, ChatGPT Apps SDK, Codex, MCP integrations, endpoint schemas, parameters, limits, or migrations and you need up-to-date official guidance.

    The same file is in 4 other repositories

  • Read github

    autohandai/community-skills/read-github Skill

    10★ repo

    Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo

    The same file is in 3 other repositories

  • Technical writing

    autohandai/community-skills/technical-writing Skill

    10★ repo

    Write clear, comprehensive technical documentation. Use when creating specs, architecture docs, runbooks, or API documentation. Handles technical specifications, system design docs, operational guides, and developer documentation with industry best practices.

    The same file is in 3 other repositories

  • User guide writing

    autohandai/community-skills/user-guide-writing Skill

    10★ repo

    Write clear and helpful user guides and tutorials for end users. Use when creating onboarding docs, how-to guides, or FAQ pages. Handles user-focused documentation, screenshots, step-by-step instructions.

    The same file is in 3 other repositories

  • Writing plans

    autohandai/community-skills/writing-plans Skill

    10★ repo

    Use when you have a spec or requirements for a multi-step task, before touching code

    The same file is in 6 other repositories

  • Writing skills

    autohandai/community-skills/writing-skills Skill

    10★ repo

    Use when creating new skills, editing existing skills, or verifying skills work before deployment

    The same file is in 7 other repositories

  • Xlsx

    autohandai/community-skills/xlsx Skill

    10★ repo

    Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

    The same file is in 1 other repository

  • Document

    huzaifa525/claude-code-optimizer/templates/.claude/skills/document Skill

    9★ repo

    Use when the user wants to add documentation, JSDoc, docstrings, or API docs to existing code.

  • Handoff

    yamanidev/claude-code-configuration/skills/handoff Skill

    9★ repo

    Workflow for compacting the current conversation into a handoff document that another Claude Code session can pick up from later. Produces a single Markdown file capturing the goal, current state, in-flight work, decisions made, open questions, paths touched, and a recommended next-session skill — referencing existing artifacts (commits, PRs, diffs, plan docs, tickets, ADRs) by path or URL rather than duplicating them. NOT for writing tickets for a human development team (use /write-task for that) and NOT for permanent documentation of decisions (commits, ADRs, or the codebase own that).

  • Write task

    yamanidev/claude-code-configuration/skills/write-task Skill

    9★ repo

    Workflow for turning a feature, change, or bug into a well-scoped ticket for a development team. May read code to understand the system well enough to write a good ticket — but the output is product-level, not an implementation plan. Produces concise tickets focused on the problem, behavior, and acceptance criteria. Does not implement the change (use /ship).

  • Adept writing tests

    itaywol/adeptability/.adeptability/base/adept-writing-tests Skill

    9★ repo

    How to write tests in the adept Go codebase — table-driven tests with testify, golden fixtures under testdata/, the cmd/adept e2e harness, temp-dir/HOME isolation, and coverage gates. Apply when adding or changing Go tests here. (matches: **/*_test.go)

  • Adept writing tests

    itaywol/adeptability/.adeptability/skills/adept-writing-tests Skill

    9★ repo

    How to write tests in the adept Go codebase — table-driven tests with testify, golden fixtures under testdata/, the cmd/adept e2e harness, temp-dir/HOME isolation, and coverage gates. Apply when adding or changing Go tests here. (matches: **/*_test.go)

  • Adept writing tests

    itaywol/adeptability/.adeptability/staging/.claude/skills/adept-writing-tests Skill

    9★ repo

    How to write tests in the adept Go codebase — table-driven tests with testify, golden fixtures under testdata/, the cmd/adept e2e harness, temp-dir/HOME isolation, and coverage gates. Apply when adding or changing Go tests here. (matches: **/*_test.go)

  • Adept writing tests

    itaywol/adeptability/.adeptability/staging/skills/adept-writing-tests Skill

    9★ repo

    How to write tests in the adept Go codebase — table-driven tests with testify, golden fixtures under testdata/, the cmd/adept e2e harness, temp-dir/HOME isolation, and coverage gates. Apply when adding or changing Go tests here. (matches: **/*_test.go)

  • Adept writing tests

    itaywol/adeptability/skills/adept-writing-tests Skill

    9★ repo

    Cross-harness AI skill portability CLI. Author an agent skill once, sync it into Claude Code, Cursor, Copilot, Codex, OpenCode & 45+ AI coding agents. Safety scanner, content-hash drift detection. A package manager / dotfiles for AI coding agent skills.

  • Kb fediverse federation md

    reiver/vibefed/skills/kb-fediverse-federation-md Skill

    no license9★ repo

    Background knowledge about FEP-67ff FEDERATION.md, the convention for documenting federation behavior in Fediverse projects. Covers the specification requirements (valid Markdown, repository root location), suggested template sections (protocols, FEPs, ActivityPub details), machine-readable discovery via NodeInfo 2.1 software.repository, the companion FEP-c893 (DOAP JSON-LD for automated capability discovery), the origin story (Darius Kazemi's 2020 proposal, WriteFreely as first adopter), the interoperability documentation gap FEDERATION.md solves, real-world examples from Mastodon and WordPress, and the 40+ implementations that have adopted it. Load when the user asks about FEDERATION.md; how to document federation behavior; FEP-67ff; what protocols or FEPs a project supports; how to create interoperability documentation for a Fediverse project; how other projects document their ActivityPub implementation; or machine-readable federation capability discovery with DOAP.

    The same file is in 2 other repositories

  • Kb fediverse json ld

    reiver/vibefed/skills/kb-fediverse-json-ld Skill

    no license9★ repo

    Background knowledge about how JSON-LD works on the Fediverse and in ActivityPub, including the difference between @id and id, @type and type (keyword aliasing via @context), the many forms a value can take (string, object with @value, object with @id, array, language-tagged value), the four JSON-LD document forms (compacted, expanded, flattened, framed), how @context works and when it is optional, why most Fediverse implementations treat JSON-LD as plain JSON and what breaks when they do, the content vs contentMap language map pattern, the functional vs non-functional property distinction, content type negotiation (application/activity+json vs application/ld+json), LD Signatures and JSON-LD canonicalization, Mastodon's @context structure and known bugs, and defensive parsing strategies. Load when the user asks about JSON-LD in ActivityPub, why @id and id are equivalent, how to handle value form variability, how to construct or interpret a @context, why a property can be a string or an array, how expansion or compaction works, how to add extensions to ActivityPub, content type headers for ActivityPub requests, or when reviewing or writing code that parses, produces, or transforms ActivityPub JSON-LD documents.

    The same file is in 2 other repositories

  • Kb kbin

    reiver/vibefed/skills/kb-kbin Skill

    no license9★ repo

    Background knowledge about Kbin and its active community fork Mbin, the decentralized content aggregator and microblogging platform for the Fediverse (Reddit + Mastodon hybrid). Covers the dual content model (threads/link aggregation via Page objects + microblogging via Note objects in a single platform), magazines as Group actors with Announce relay (same pattern as Lemmy communities), the three actor types (Application instance actor at /i/actor, Person user at /u/username, Group magazine at /m/name), supported activities (Follow, Like, Announce, Create, Update, Delete, Block, Flag, Lock, Add, Remove), the critical detail that downvotes do NOT federate, content object mapping (threads as Page, microblogs as Note, comments as Note with inReplyTo, private messages as ChatMessage), the tech stack (PHP 8.2+/Symfony/PostgreSQL/RabbitMQ/Redis, AGPL-3.0), the REST API with OAuth2 and Swagger docs at /api/docs, the Mbin fork history (Kbin discontinued after creator Ernest Wisniewski's absences, Mbin forked October 2023 with C4 governance, improved federation/performance/ scaling), Kbin vs Lemmy comparison (Kbin has microblogging + threads while Lemmy is threads only, Kbin has stronger Mastodon integration, Lemmy federates downvotes while Kbin does not), the Threadiverse ecosystem context (Lemmy, Mbin, PieFed, Sublinks), voting/reputation system (reputation is cosmetic only), and federation interoperability details. Load when the user asks about Kbin or Mbin; implementing a Kbin/Mbin-compatible ActivityPub server; how Kbin magazines federate as Group actors; how Kbin combines link aggregation and microblogging; why Kbin downvotes don't federate; the Kbin to Mbin transition; how Kbin/Mbin differs from Lemmy; interoperating with Kbin/Mbin instances; the Threadiverse; or building software that federates with Kbin/Mbin.

    The same file is in 2 other repositories

  • Kb writefreely

    reiver/vibefed/skills/kb-writefreely Skill

    no license9★ repo

    Background knowledge about WriteFreely, the open-source federated blogging platform written in Go (AGPL-3.0) by Matt Baer / Musing Studio. Covers the origin story (Write.as anonymous writing platform launched 2014, open-sourced as WriteFreely November 2018 after adding ActivityPub), the write-only/broadcast federation model (blogs can be followed but cannot follow others, no incoming comments/replies displayed, no moderation), the actor model (each blog/collection is a Person actor with handle @[email protected]), the Article vs Note object type distinction (double-line break heuristic, notes_only config option), supported activities (outbound Create/Update/Delete, inbound Follow/Undo/Like), RSA-SHA256 HTTP signatures with per-blog keypairs, the tech stack (Go/MySQL or SQLite/single binary deployment/256 MB RAM/Raspberry Pi), configuration (single-user vs multi-user modes, federation toggle, .ini config file), NodeInfo with WriteFreely-specific metadata, the RESTful API (Posts/Collections/Users with token auth, anonymous publishing), the Musing Studio ecosystem (Write.as, WriteFreely.host, Snap.as, Remark.as, Submit.as, Read.as), Gopher protocol support, Web Monetization, email newsletters, custom CSS/JS per blog, OAuth 2.0 integration, comparison with Plume and Ghost. Load when the user asks about WriteFreely; implementing a WriteFreely-compatible ActivityPub server; how WriteFreely blogs federate; WriteFreely's Article vs Note distinction; WriteFreely's write-only federation model; WriteFreely's API; the Write.as and Musing Studio ecosystem; federating with WriteFreely instances; long-form blogging in the Fediverse; or building software that interoperates with WriteFreely.

    The same file is in 2 other repositories

  • Readme writing

    vanara-agents/skills/skills/readme-writing Skill

    9★ repo

    How to write a README that gets a project understood and running fast — lead with what/why, a 60-second quickstart, then usage, config, contributing, and license. Covers required sections, show-don't-tell examples, scannability, badges, and failure modes. Use when writing or auditing a project README.

  • Test driven development

    endorphin-ai/hasbrains-agent-kit/agent-engineering/skills/test-driven-development Skill

    9★ repo

    The battle-tested Claude Code kit behind HasBrainsAI — agent skills, subagents & slash commands for production multi-agent systems. Install in one command.

  • Soc media writer

    endorphin-ai/hasbrains-agent-kit/content-creation/skills/soc-media-writer Skill

    9★ repo

    The battle-tested Claude Code kit behind HasBrainsAI — agent skills, subagents & slash commands for production multi-agent systems. Install in one command.

  • Pipeline state

    endorphin-ai/hasbrains-agent-kit/context-engineering/skills/pipeline-state Skill

    9★ repo

    The battle-tested Claude Code kit behind HasBrainsAI — agent skills, subagents & slash commands for production multi-agent systems. Install in one command.

  • Prompt expert

    endorphin-ai/hasbrains-agent-kit/context-engineering/skills/prompt-expert Skill

    9★ repo

    The battle-tested Claude Code kit behind HasBrainsAI — agent skills, subagents & slash commands for production multi-agent systems. Install in one command.

  • Designer frontend contract

    endorphin-ai/hasbrains-agent-kit/web-dev/skills/designer-frontend-contract Skill

    9★ repo

    The battle-tested Claude Code kit behind HasBrainsAI — agent skills, subagents & slash commands for production multi-agent systems. Install in one command.

  • Docs analysis

    ellmos-ai/skills/skills/dev/docs-analysis Skill

    9★ repo

    Document requirements analysis: Analyzes concept and requirements documents in the docs/ folder, checks requirements against current code, and creates a consolidated difference report.

  • Document chunker

    ellmos-ai/skills/skills/utilities/document-chunker Skill

    9★ repo

    Dokumente in ueberlappende Token-Chunks aufteilen fuer RAG-Pipelines und LLM-Kontextfenster. Zero Dependencies.

  • Privat mail writer

    ellmos-ai/skills/skills/utilities/privat-mail-writer Skill

    9★ repo

    Dieser Skill sollte genutzt werden, wenn der User private oder halbformale E-Mails schreiben, beantworten, absagen, nachfassen, kürzen, umformulieren oder im eigenen Stil entwerfen lassen will, besonders bei Terminen, offiziellen Absagen, freundlichen Kurzantworten und kontaktabhängigem Ton. Profilanalyse erst bei einem konkreten Mail-Schreibauftrag starten.

  • Peec report

    AntonioBlago/peec-ai-skills/skills/peec-report Skill

    9★ repo

    Weekly / monthly closed-loop reporter for Peec AI visibility growth. Measures what moved (visibility per prompt, cluster, zone) against what was invested (content published, pitches sent, forum answers), detects winning patterns, and outputs a ranked next-actions list — not a dashboard. Closes the feedback loop for the growth agent. Use weekly for active projects or monthly for maintenance-mode.

  • Go documentation

    muratmirgun/gophers/skills/go-documentation Skill

    9★ repo

    Use when writing or reviewing Go documentation — godoc comments on packages, types, functions, methods, sentinel errors; runnable Example tests; README/CONTRIBUTING/CHANGELOG. Covers the project-type detection (library vs application) that decides which docs are needed, comment grammar (start with name, full sentences), what to document vs what to skip, and Example test conventions. Apply proactively when introducing exported names, even if documentation was not requested.

  • Go swagger

    muratmirgun/gophers/skills/go-swagger Skill

    9★ repo

    Use when adding or maintaining OpenAPI/Swagger documentation for a Go HTTP API. Covers swaggo/swag annotation comments (@Summary, @Param, @Success, @Router, @Security), the swag CLI workflow, framework integration for Gin/Echo/Fiber/Chi/net-http, security definitions (Bearer/JWT, OAuth2, API key), and struct tags (example, enums, swaggertype, swaggerignore). Apply when a project imports github.com/swaggo/swag or any of the swaggo UI adapters, or when you need to expose /swagger/index.html.

  • Finding docs

    isvlasov/rageatc-oss/plugins/rageatc-code-oss/skills/finding-docs Skill

    9★ repo

    Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — including well-known ones like React, Next.js, Prisma, Django, or Spring Boot. Use for API syntax, configuration, version migration, setup, and library-specific debugging. Use even when you think you know the answer — training data and web search are frequently outdated for API details.

  • Communicating in writing

    isvlasov/rageatc-oss/plugins/rageatc-core-oss/skills/communicating-in-writing Skill

    9★ repo

    Guides written communication — emails, reports, presentations, documents, website copy, newsletters, books. Use when writing or improving writing, adapting to an audience, or shaping document structure. Not for oral delivery or tool-specific formatting (slides, PDFs).

  • Debloating

    isvlasov/rageatc-oss/plugins/rageatc-core-oss/skills/debloating Skill

    9★ repo

    Raises an artefact's signal-to-noise ratio by removing text that earns nothing for its reader — filler, repetition, over-explanation, ornamental phrasing — and relocating conditional detail to references. Use to slim a skill, agent, or document, cut bloat, tighten prose, or shrink a file that has grown too long. Tuned for SKILL.md files.

  • Writing skills

    isvlasov/rageatc-oss/plugins/rageatc-core-oss/skills/writing-skills Skill

    9★ repo

    Creates and updates Claude Code Agent Skills. Use when creating a skill, revising SKILL.md, improving a skill's name or description, or adding progressive disclosure files.

  • Design analysis

    narrative-io/narrative-skills-marketplace/plugins/narrative-common/skills/design-analysis Skill

    9★ repo

    Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "scope this analytical question". (narrative-common)