agentsclimarketplace

Docs & writing

16,621 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

  • Cerebrate

    jppuche/Ignite/_workflow/templates/skills/cerebrate Skill

    0★ repo

    Intelligent reflection on session knowledge. Harvests explicit facts and implicit insights, analyzes through 4 strategic lenses (Confirms, Challenges, Opens, Windows), presents intelligence brief, then persists premium documentation. Use when: end of session, after research, after strategy conversations, or when user says "cerebrate", "consolidate", "reflect", "update docs".

  • Copywriting

    DariuszCiesielski/polish-agent-skills/skills/marketing/copywriting Skill

    0★ repo

    Copy marketingowy SaaS: homepage, landing page, pricing, feature pages, email, social. Formuły: PAS, AIDA, BAB, 4U, StoryBrand. Triggery: "napisz copy", "copywriting", "tekst na landing page", "nagłówek", "headline", "CTA", "opis produktu", "tekst marketingowy", "value proposition", "USP", "przepisz stronę".

  • Celebration note writer

    stephenrogan/csm-skills/skills/celebration-note-writer Skill

    0★ repo

    Writes genuine notes celebrating customer milestones, achievements, team successes, or personal events. Avoids corporate platitudes in favour of specific, personal recognition that strengthens the relationship. Use when asked to write a congratulations note, celebrate a customer milestone, acknowledge a personal or professional achievement, mark an anniversary, or when any positive event at a customer account deserves recognition. Also triggers for questions about customer recognition, milestone celebration, relationship-building touches, congratulatory communications, or how to acknowledge customer achievements genuinely.

  • Escalation brief writer

    stephenrogan/csm-skills/skills/escalation-brief-writer Skill

    0★ repo

    Writes structured escalation documents that get the right people to act on a customer issue. Includes the headline, timeline, customer impact, resolution attempts, specific ask, and commercial context. Use when asked to write an escalation brief, document an escalation, prepare an internal escalation report, structure a request for engineering or product help, or when a customer issue needs to be routed to a team that has no context on the account. Also triggers for questions about escalation documentation, internal issue briefs, cross-functional requests, or how to write an escalation that actually gets acted on.

  • Escalation decision framework

    stephenrogan/csm-skills/skills/escalation-decision-framework Skill

    0★ repo

    Helps a CSM decide whether to escalate an issue, when to escalate, to whom, at what severity, and how to frame it. Distinct from the escalation-brief-writer (which structures the escalation document) -- this skill helps with the judgment call of whether escalation is the right move. Use when asked to decide whether to escalate, determine the right escalation level, assess whether an issue warrants internal attention beyond the CSM, or when a CSM is unsure whether a customer issue is "bad enough" to escalate. Also triggers for questions about escalation judgment, severity assessment, when to involve leadership, whether to escalate or handle it yourself, or how to decide the right escalation level.

  • Executive briefing writer

    stephenrogan/csm-skills/skills/executive-briefing-writer Skill

    0★ repo

    Condenses account context into structured executive summaries of varying depth -- from a 30-second verbal brief to a one-page written summary. Formats for the specific executive audience (your leadership, the customer's leadership, or both). Use when asked to prepare an executive briefing, write an account summary for leadership, create a board-level overview, condense account information for a VP or CRO, or when a CSM needs to brief someone senior quickly. Also triggers for questions about executive summaries, leadership briefings, account snapshots for management, or condensing complex account situations into executive-ready formats.

  • Follow up email writer

    stephenrogan/csm-skills/skills/follow-up-email-writer Skill

    0★ repo

    Writes post-meeting follow-up emails that reinforce commitments, document decisions, and maintain momentum. Produces a customer-facing email that both parties can reference as the record of what was agreed. Use when asked to write a follow-up email, draft a post-meeting recap, summarise a call in an email, document next steps after a meeting, or when a CSM needs to send a professional recap after any customer interaction. Also triggers for questions about post-meeting communication, follow-up email drafting, commitment documentation, or meeting recap emails.

  • Internal debrief writer

    stephenrogan/csm-skills/skills/internal-debrief-writer Skill

    0★ repo

    Generates an internal-only post-meeting summary that includes context a CSM would never share with the customer -- political observations, relationship assessments, competitive intelligence, strategic notes, and honest sentiment reads. Distinct from follow-up emails (customer-facing) and meeting outcome logs (CRM-facing). Use when asked to write an internal debrief, document internal observations from a meeting, create a confidential post-meeting analysis, capture relationship intelligence, or when a CSM needs to record what they actually think happened versus what they would share externally. Also triggers for questions about internal meeting analysis, confidential account observations, political dynamics documentation, or candid post-meeting notes for the team.

  • Internal status update writer

    stephenrogan/csm-skills/skills/internal-status-update-writer Skill

    0★ repo

    Compiles account portfolio status into formatted internal updates for leadership, cross-functional teams, or manager reviews. Adapts detail and framing by audience. Use when asked to write a status update, compile a portfolio summary for leadership, create a weekly report for your manager, draft a cross-functional update on key accounts, or when any internal audience needs a structured view of account status. Also triggers for questions about internal reporting, portfolio status updates, manager updates, leadership summaries, or how to communicate account status to internal stakeholders.

  • Meeting outcome logger

    stephenrogan/csm-skills/skills/meeting-outcome-logger Skill

    0★ repo

    Structures what happened in a customer meeting into a CRM-ready activity record with outcome classification, sentiment assessment, next steps, and follow-up triggers. Bridges the gap between "the meeting happened" and "the system knows what happened." Use when asked to log a meeting outcome, create a CRM activity record, document what happened in a call, classify a meeting result, or when any customer interaction needs to be recorded in a structured format for downstream use. Also triggers for questions about meeting documentation, activity logging, CRM record creation, or structured meeting capture.

  • Re engagement email writer

    stephenrogan/csm-skills/skills/re-engagement-email-writer Skill

    0★ repo

    Writes outreach to customers who have gone dark -- not responded to recent communications, missed meetings, or disengaged from the product. Differs from a check-in email by acknowledging the silence and offering a specific reason to re-engage rather than asking if everything is fine. Use when asked to write a re-engagement email, reach out to a silent customer, draft an outreach to a customer who has gone dark, break through to an unresponsive contact, or when a no-reply streak indicates the customer has disengaged. Also triggers for questions about customer silence, unresponsive accounts, re-engagement strategy, or breaking through communication barriers.

  • Squid perf

    subsquid-labs/skills/squid-sdk/squid-perf Skill

    no license0★ repo

    Compare sync-time performance across one or more Squid SDK deployments. Fetches logs via sqd CLI, parses per-service progress, and generates a self-contained HTML report plus a Markdown summary with wall-clock/active-time/downtime breakdowns at log-spaced block breakpoints. Supports single-indexer mode (metrics only, no comparison). Use when the user invokes "/squid-perf", asks to compare Squid deployment sync times, or references squid performance profiling.

  • Content strategy

    planifest/planifest-framework/planifest-framework/external-skills/content-strategy Skill

    0★ 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 2 other repositories

  • Copywriting

    planifest/planifest-framework/planifest-framework/external-skills/copywriting Skill

    0★ 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

  • Document release

    planifest/planifest-framework/planifest-framework/external-skills/document-release Skill

    0★ repo

    Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped. (gstack)

  • Documentation and adrs

    planifest/planifest-framework/planifest-framework/external-skills/documentation-and-adrs Skill

    0★ repo

    Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

    The same file is in 11 other repositories

  • Documentation api reference

    planifest/planifest-framework/planifest-framework/external-skills/documentation-api-reference Skill

    0★ repo

    Author API reference documentation that is accurate, complete, and implementation-aligned for client developers. Use when API docs are primary deliverables or must be updated for contract changes; do not use for implementing new product behavior.

  • Documentation architecture

    planifest/planifest-framework/planifest-framework/external-skills/documentation-architecture Skill

    0★ repo

    Author architecture documentation that explains boundaries, dependencies, and operational constraints for engineering decision-making. Use when architecture docs are primary deliverables or must be updated after structural changes; do not use for implementing production feature logic.

  • Documentation rfc

    planifest/planifest-framework/planifest-framework/external-skills/documentation-rfc Skill

    0★ repo

    Author RFC documents for proposed technical changes with clear problem framing, options, tradeoffs, and decision path. Use when proposal alignment and review sign-off are needed before implementation; do not use for post-decision implementation-only docs.

  • Git release tagging

    planifest/planifest-framework/planifest-framework/external-skills/git-release-tagging Skill

    0★ repo

    Create immutable release tags and traceable release notes from Git history. Use when release cuts require consistent tag naming, immutability guarantees, and bounded changelog traceability; do not use for CI workflow design or application behavior implementation.

  • Localization qa

    planifest/planifest-framework/planifest-framework/external-skills/localization-qa Skill

    0★ repo

    Localization QA workflow for language correctness, layout resilience, and locale-specific behavior validation before release. Use when localized UI/content must be verified across target locales; do not use for backend data-model or deployment pipeline decisions.

  • Okr writing

    planifest/planifest-framework/planifest-framework/external-skills/okr-writing Skill

    0★ repo

    Write effective Objectives and Key Results that align teams, communicate priorities, and drive measurable outcomes — not vanity metrics or activity tracking

  • Runbook authoring

    planifest/planifest-framework/planifest-framework/external-skills/runbook-authoring Skill

    0★ repo

    Runbook authoring workflow for clear, executable operational procedures for on-call responders. Use when incident response, rollback, failover, or maintenance steps must be documented before production use; do not use for production feature logic design.

  • Sales enablement

    planifest/planifest-framework/planifest-framework/external-skills/sales-enablement Skill

    0★ repo

    When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.

    The same file is in 2 other repositories

  • User story writing

    planifest/planifest-framework/planifest-framework/external-skills/user-story-writing Skill

    0★ repo

    User story authoring workflow for turning prioritized requirements into implementable, testable delivery slices. Use when approved requirement work must be decomposed for sprint execution; do not use for initial requirement discovery or release-level prioritization.

  • Writing plans

    planifest/planifest-framework/planifest-framework/external-skills/writing-plans Skill

    0★ repo

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

    The same file is in 12 other repositories

  • Planifest docs agent

    planifest/planifest-framework/planifest-framework/skills/planifest-docs-agent Skill

    0★ repo

    Produces complete per-component documentation, system-wide registry, dependency graph, and iteration log audit trail. Invoked during the Documentation step.

  • Planifest test writer

    planifest/planifest-framework/planifest-framework/skills/planifest-test-writer Skill

    0★ repo

    TDD red phase — writes exactly one failing test per requirement and confirms RED (non-zero exit). Invoked by planifest-codegen-agent for each requirement in the TDD inner loop.

  • Writing plans

    brothaakhee/superclaw/writing-plans Skill

    no license0★ repo

    Use when you have a spec or approved design before implementation

  • Figma implement design

    michelve/hugin-v0/skills/figma-implement-design Skill

    0★ repo

    Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.

  • Writing tests

    michelve/hugin-v0/skills/writing-tests Skill

    0★ repo

    Use this skill when writing, reviewing, or improving tests. Trigger on: 'write tests', 'add tests', 'test naming', 'what should I test', 'edge cases', 'test structure', 'assertion', 'toBe vs toEqual', 'toBeDefined', 'toBeTruthy', 'test review', 'test quality', 'test coverage', 'how to test', 'bug found write test', 'one test enough', 'test name', 'arrange act assert', 'AAA pattern'. Also trigger when user shares a test and asks for review, asks about assertion best practices, asks what edge cases to consider, mentions test names like 'test login' or 'should work', asks about splitting tests, or reports finding a bug and wants to know what else to test. Do NOT trigger for test runner configuration (jest.config, vitest.config), CI/CD pipeline setup, or questions about testing frameworks that aren't about how to write the tests themselves.

  • Prd

    mifunedev/skills/skills/prd Skill

    0★ repo

    Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

  • Doc coauthoring

    jeffchen006/skills/.agent/skills/doc-coauthoring Skill

    no license0★ 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

  • Doc coauthoring

    jeffchen006/skills/.claude/skills/doc-coauthoring Skill

    no license0★ 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

  • Tech writer

    sungkhum/agent-skills-pack/tech-writer Skill

    no license0★ repo

    Standalone technical writer agent. Use when the user asks to write or update technical documentation, create Mermaid diagrams, explain complex concepts, validate docs against standards, or generate comprehensive project documentation.

  • Critique grimoire

    abetatos/seed-grimoire/.claude/skills/critique-grimoire Skill

    no license0★ repo

    Adversarial structural review of `output/<series>/grimoire.md` — the world grimoire. Audits the foundational worldbuilding document BEFORE `book-setup` or `plan-book` run, so that the per-book plan never inherits a flawed foundation. Use this when the user says "audita el grimorio" / "critique the grimoire" / "is the grimoire ready?" Invoke after writing or revising the grimoire, and before running `book-setup` for a new book in the series.

  • Plan chapter

    abetatos/seed-grimoire/.claude/skills/plan-chapter Skill

    no license0★ repo

    Pre-chapter decision gate. BEFORE write-chapter runs, build a short briefing of the upcoming chapter (its job, the seeds due with their trigger/dose/resolution, the emotional-spine touch, Bruno-or-POV exposure state) and surface the 2-4 creative forks the outline leaves underdetermined as AskUserQuestion choices WITH a recommendation each. Persist the author's answers to notes/decisions-chNN.md so write-chapter honors them and a regeneration cannot silently overwrite them. Use this as the FIRST step of writing any chapter — invoke as "plan chapter N" / "briefing for chapter N"; write-novel chains it before write-chapter.

  • Search corpus

    abetatos/seed-grimoire/.claude/skills/search-corpus Skill

    no license0★ repo

    Targeted grep across a book's canon, plan, summaries, and chapter prose. Tier priority canon > plan > summary > chapter. Use this when the writer needs to recall a specific named character, place, magic term, or earlier line without loading every file into context. Invoke as "search for X in book N" or "where did we mention X?"

  • Write chapter

    abetatos/seed-grimoire/.claude/skills/write-chapter Skill

    no license0★ repo

    Write a single chapter of the book in the declared language, writing to the structural budget (every beat in the beat sheet; length is never counted), using the assembled deterministic context (setup + canon + plan + shadow + seed envelope + recent chapters). Use this when the user says "write chapter N", "next chapter", or "continue". Refuses if the chapter's outline beat sheet is empty.

  • Write novel

    abetatos/seed-grimoire/.claude/skills/write-novel Skill

    no license0★ repo

    Top-level orchestrator that drives a book from a starting chapter through the end of the book, chaining plan-chapter (decision gate) → write-chapter → expand-chapter (always, grounding pass) → critique-chapter → (revise/expand if needed) → update-canon → (close-act at act ends) for ONE chapter, then HARD STOPS for a `/clear` before the next chapter. The project standard is one chapter per session (state lives on disk; the next session rebuilds via resume-act). Use this when the user says "write the next chapter" / "drive chapter N" / "continue the book".

  • Write a prd

    muhammadrivaldy/agent-skills/write-a-prd Skill

    no license0★ repo

    Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

    The same file is in 3 other repositories

  • Webpage capture markdown

    yangshu2087/Codex/.agents/skills/webpage-capture-markdown Skill

    no license0★ repo

    Capture an external webpage into a reusable local markdown note. Use when the user wants a rendered page saved locally, preserved for later reference, or turned into a markdown source artifact rather than only summarized in chat.

  • Playwright best practices

    yangshu2087/Codex/vendor/skills/playwright-best-practices Skill

    no license0★ repo

    Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.

    The same file is in 1 other repository

  • Documentation criteria

    yangshu2087/Codex/vendor/skills/skilltrust-curated/codex-workflows/documentation-criteria Skill

    no license0★ repo

    Use when creating or reviewing PRDs, ADRs, design docs, UI specs, or work plans and a documentation template or document-type decision is needed.

  • Archive metadata

    m4tice/the-archive/.github/skills/archive-metadata Skill

    0★ repo

    Read and validate metadata on an archive document. Use when checking, fixing, or reporting on metadata fields.

  • Drift guards

    guygrigsby/claude-plugins/plugins/drift-guards/skills/drift-guards Skill

    0★ repo

    Use when a fact is about to live in more than one place (docs describing code, a README command, a catalog or config mirrored in a spec, a version string repeated across manifests, an env key in code and .env.example and a deploy unit, a status table, an onboarding doc), when writing or updating READMEs/specs/CLAUDE.md, when adding an op/endpoint/flag/config key/enum variant that something else mentions, when committing generated artifacts, or when a reviewer or user notices docs out of date. Automate everything so drift is impossible.

  • Spec research

    h3y6e/spec-skills/skills/spec-research Skill

    0★ repo

    Investigate a specific topic and record findings in specs/{feature}/research/{topic}.md — covering technical options, library comparisons, API constraints, architecture trade-offs, or any open question that needs evidence before a decision can be made. Use this skill whenever someone wants to research a topic independently of spec/plan/implement phases, compare technical alternatives, investigate an API or platform constraint, run a proof of concept and document results, or says "research [topic]". This is a utility skill that can be invoked from any point in the spec-driven workflow or standalone. Don't use for writing specs, creating plans, or implementing code.

  • Spec specify

    h3y6e/spec-skills/skills/spec-specify Skill

    0★ repo

    Create or update specs/{feature}/spec.md from user requirements — writing user stories, functional requirements, acceptance criteria, and resolving ambiguity through focused questions. Use this skill whenever someone wants to document feature requirements, write a specification, turn ideas or user research into a formal spec, update spec.md, or says "create a spec for [feature]". This is the first required step in the spec-driven workflow and typically follows spec-constitution when a team uses shared constitutional rules. Don't use for execution design, task decomposition, bug fixes, or implementation.

  • Obsidian

    lx-wnk/skills/skills/obsidian Skill

    0★ repo

    Obsidian vault access via Local REST API using curl — read, search, create, or update notes in the knowledge base. Trigger on ANY of these: user mentions "obsidian", "vault", "knowledge base", "my notes", or "note" in a save/lookup context; user asks to "save", "persist", "document", "note down", or "look up" information; phrases like "note this down", "add this to my knowledge base", "search my notes", "check if I have notes on X", "create a note"; CLAUDE.md says to search or store in Obsidian before/after tasks — do it proactively; starting a task where prior context might exist → search first; mid-task discovery of a non-obvious insight, gotcha, root cause, or workaround → save it; finishing a task with decisions or learnings worth remembering → persist it; something written to CLAUDE.md or project docs → also save it for cross-project search.

  • Oss readiness

    lx-wnk/skills/skills/oss-readiness Skill

    0★ repo

    Audits a repository for public-release ("open source") readiness: README front-door quality (Why/How/Benefits, badges, quick example, section order), doc deduplication, community-health files (LICENSE, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT, issue/PR templates), and repo signals (description, topics, CI badge, releases, .gitignore, secrets). Fans out 4 parallel dimension agents into outputs/OSS-Readiness.md, P0-P3 findings. --apply-fixes drafts missing community-health files tailored to the repo, adds a CI badge, reorders README, dedups docs — escalates subjective calls (tagline, license choice, prose voice) as TODOs, never guesses. Use for "oss readiness", "prep for public release", "audit my repo for open source", "make this repo public-ready", "readme tuning", "make it presentable", or German "fit für open source", "repo veröffentlichen", "readme aufhübschen", "public-ready machen", "oss-check". Does NOT review source-code quality/security — use /branch-review or /full-project-review.

  • Test write

    neumie/almanac/skills/other/test-write Skill

    0★ repo

    Use when backfilling tests on existing code. Detects test framework, writes behavior-focused regression tests via public interfaces. Modes: targeted (files) or diff-based (changed).

  • Grill with docs

    neumie/almanac/skills/productivity/grill-with-docs Skill

    0★ repo

    Use when stress-testing a plan against the existing domain model + decisions. Challenges terminology, cross-references code, updates CONTEXT.md and ADRs inline as decisions crystallize.

  • Write good fix

    albedo-c/custom-skills/skills/write-good-fix Skill

    no license0★ repo

    Run write-good to detect weak English prose in comments, docstrings, and documentation, then apply fixes directly using file editing tools. Use when user asks to "fix grammar", "improve writing", "check prose", "fix passive voice", or "run write-good".

  • Konecty dev

    konecty/skills/skills/konecty-dev Skill

    0★ repo

    Helps developer-agents WRITE CODE to integrate with the Konecty platform — preferring the official SDKs (Python konecty_sdk_python, Node/TS @konecty/sdk), with the full REST API documented for other languages. Covers authenticating server-side code (service-account token), find/query, create, update, delete, cross-module and SQL queries, file upload/download, and writing data hooks (scriptBeforeValidation, validationScript, scriptAfterSave). Use when: escrever código, criar integração, integrar meu app/serviço com Konecty, usar o SDK Python/Node, exemplo de código, gerar um cliente, autenticar código, escrever um hook; write code, build an integration, use the Konecty SDK, code example, generate a client, authenticate server-side, call the Konecty API, write a hook. Do NOT use to run one-off data ops now (find/create/update/delete) — use konecty-data; or to manage schema/metadata — use konecty-meta.

  • Doc coauthoring

    TheWatcher01/skills/.claude/skills/doc-coauthoring Skill

    0★ 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.

  • Docx

    TheWatcher01/skills/.claude/skills/docx Skill

    0★ 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.

  • Fix grammar

    TheWatcher01/skills/.claude/skills/fix-grammar Skill

    0★ repo

    Fix grammar and spelling errors in one or multiple files while preserving formatting

  • Harness writing

    TheWatcher01/skills/.claude/skills/harness-writing Skill

    0★ repo

    Techniques for writing effective fuzzing harnesses across languages. Use when creating new fuzz targets or improving existing harness code.

    The same file is in 4 other repositories

  • Outreach writer

    TheWatcher01/skills/.claude/skills/outreach-writer Skill

    0★ repo

    Rédiger messages outreach personnalisés CNIL-compliant depuis profil lead datalake. Email, LinkedIn, WhatsApp.

  • Prompt engineering sota

    TheWatcher01/skills/.claude/skills/prompt-engineering-sota Skill

    0★ repo

    Apply SOTA prompt engineering techniques to any task. USE when: improving AI responses, structuring complex instructions, debugging poor outputs, choosing between CoT/ToT/ReAct, writing system prompts, or any task needing optimal LLM interaction. Covers 40+ techniques from Zero-shot to Tree-of-Thought, ReAct, Reflexion, Self-Consistency. Optimized for fast models (Haiku 4.5, Llama 3.1 8B). Trigger: "improve this prompt", "the AI gives bad answers", "write a system prompt", "use chain of thought".