Docs & Writing
Docs & writing agent skills turn AI agents into dependable technical writers: READMEs, API references, PDFs and Word documents, changelogs, and style-guide enforcement. Install one and your agent produces the same structure and tone every time it writes.
-
bkjohn2018 Skill Process And Procedure WritingWrites clear process and procedure documentation with roles, steps, controls, and handoff criteria. Use when documenting repeatable operational workflows.
-
dirtytrii Bundle Gstack QA OnlyGStack report-only QA method for checking web or UI behavior, documenting blockers, and preserving evidence without modifying code.
-
dirtytrii Bundle Gstack Document ReleaseGStack release documentation method for changelog, release notes, announcement copy, and internal/external release communication.
-
pedroiff0 Bundle PowerpointCreate, read, edit .pptx decks, slides, notes, templates.
-
fworks-tech Skill APIUse when designing, building, or testing REST APIs — endpoint design, authentication, error handling, pagination, versioning, and OpenAPI documentation. Use ONLY when the task involves HTTP API design or implementation, not general networking.
-
fworks-tech Skill The LibrarianCreates and maintains documentation, READMEs, ADRs, and API references. Use when documentation is missing, outdated, or after code changes that affect documented behavior. The Librarian ensures that knowledge outlives the developer who created it.
-
fworks-tech Skill Concept ExplainerBreaks down complex technical concepts in beginner-friendly ways with analogies, practical examples, and understanding checks. Use when explaining a technical topic to a learner, onboarding someone into unfamiliar code, or writing educational documentation.
-
fworks-tech Skill Cleanup SpecialistRemoves dead code, eliminates duplication, refactors messy patterns, and applies consistent formatting across code and documentation — safely, with tests before and after. Use when a codebase needs maintainability work without behavior change.
-
2428424081cn Bundle Meeting Notes从会议记录文本提取要点、发言人统计与待办事项,输出结构化 Markdown 纪要。
-
kir-kopylov Bundle Dopsoglasheniya Po Oplate«ДС по постоплате», «допник по оплате», «дополнительное соглашение на вычет», «измени сумму аренды допсоглашением», «ДС к договору найма». Сборка DOCX.
-
kir-kopylov Bundle Verstka DOCX Po Standartu«Свёрстай договор или расписку в docx по стандарту», «отрендери готовый текст в Word», «собери Word-файл из готовой структуры — шрифт и поля». Times New Roman, A4.
-
cleanexpo Skill PDF Generator 2PDF Generator
-
cleanexpo Skill Report Generator 2Report Generator
-
cleanexpo Skill Markdown Processor 2Markdown Processor
-
smirnovalex-qa Skill E2e Test AuthorDesigns and writes E2E/UI automated tests for a user flow, screen, or form, then actually runs them and fixes them until the run is green. First it detects which E2E stack the repository already uses (Playwright / Cypress / Selenium / WebdriverIO — from package.json/dependencies/existing tests/CI) and writes in that stack's conventions rather than imposing a new one. It designs scenarios from requirements using the use-case technique (happy path + alternative + negative + edge), builds a resilient architecture (Page Object, fixtures, isolation), makes the tests non-flaky (role/testid locators, auto-waiting instead of sleep), and reports the actual run output. Use when asked to "write e2e tests", "automate this scenario in the browser", "playwright/cypress tests for this page", "cover a user flow with automated tests", "e2e for the login/checkout/registration form", "run this UI scenario automatically" — even if the word "e2e" is not said literally and the request is about "automated tests for the interface",
-
smirnovalex-qa Skill Bug Report WriteHelps you put together a short, informative bug report in a fixed structure (Title, Description, Priority, Status, Date found, Steps to reproduce, Expected result, Actual result). Use when asked to write/draft/put together a bug report or defect report from a problem description.
-
smirnovalex-qa Skill I18N L10n ReviewInternationalization (i18n) and localization (l10n) review — scope from a feature/screen/directory/branch, a requirements document, or a tracker issue; checking hardcoded strings, translation completeness, UI overflow on long languages, RTL support, pluralization, date/number/currency/time formats by locale, time zones, unicode, and variable interpolation, with a live run across locales in the browser. Every finding is tied to file:line, the specific breaking locale/language, and a scenario, with an explicit verdict on multilingual readiness. Use when asked to check localization, do an i18n/l10n review, assess support for other languages, find hardcoded user-facing strings, verify whether the layout will break on long translations or on RTL (Arabic/Hebrew), or whether dates/numbers/currencies are formatted correctly by locale — even without the word "review", e.g. "is there any hardcoded text here", "will this work in German", "did we really translate everything", "why is the date shown in American format", "
-
smirnovalex-qa Skill Bug Report Write 2Помогает составить короткий, информативный баг-репорт в фиксированной структуре (Название, Описание, Приоритет, Статус, Дата обнаружения, Шаги для воспроизведения, Ожидаемый результат, Фактический результат). Используй когда просят написать/оформить/составить баг-репорт или отчёт об ошибке по описанию проблемы.
-
smirnovalex-qa Skill Test Summary ReportProduces a Test Summary Report (QA sign-off) for stakeholders on a cycle/release — what was and wasn't tested, a summary of case results (passed/failed/blocked/skipped) and requirements coverage, defects found by severity, residual risks and known issues, non-functional results, quality metrics, a verdict-recommendation, and appendices with links. Use when asked for a "test report", "test summary report", "testing results for a release/cycle", "QA sign-off", "what was tested and with what result", "a report on the test-cycle run", "a quality summary for management", "a testing recap before release" — even if the term isn't said and it's phrased as "pull together what we tested", "we need a document for stakeholders about the release quality", "wrap up the QA". Tone — for management (executive summary without jargon) plus technical appendices. Data is gathered from CI/the tracker/previous reports in docs/qa; when data is missing the skill honestly flags the gaps rather than inventing numbers.
-
smirnovalex-qa Skill Bug Report Verify 2Адверсариально проверяет валидность баг-репорта — не оформление, а саму проблему по первоисточникам (код, спека, git history), с попыткой опровергнуть репорт прежде чем подтвердить его. Используй, когда просят проверить/провалидировать/подтвердить баг-репорт, усомниться в баг-репорте, или перед тем как начинать работу над заведённым багом, чтобы убедиться что он реальный, а не галлюцинация агента.
-
smirnovalex-qa Skill Defect Metrics ReportDefect metrics report
-
smirnovalex-qa Skill Test Summary Report 2Формирует итоговый отчёт о тестировании (Test Summary Report, QA sign-off) для стейкхолдеров по циклу/релизу — что тестировалось и что нет, сводка результатов кейсов (passed/failed/blocked/skipped) и покрытия требований, найденные дефекты по severity, остаточные риски и known issues, нефункциональные результаты, метрики качества, вердикт-рекомендация и приложения со ссылками. Используй когда просят «отчёт о тестировании», «test summary report», «итоги тестирования релиза/цикла», «QA sign-off», «что протестировано и с каким результатом», «отчёт по прогону тест-цикла», «сводку для менеджмента по качеству», «резюме тестирования перед релизом» — даже если термин не произнесён, а говорят «собери, что мы натестили», «нужен документ для стейкхолдеров про качество релиза», «подведи итоги QA». Тон — для менеджмента (executive summary без жаргона) плюс технические приложения. Данные собираются из CI/трекера/предыдущих отчётов в docs/qa; при отсутствии данных скилл честно помечает пробелы, а не выдумывает цифры.
-
smirnovalex-qa Skill Defect Metrics Report 2Отчёт по метрикам дефектов
-
lhh666-6 Skill Bib ParseExtract citations from a PDF and generate a validated .bib file. Reads the PDF, identifies all referenced works, constructs BibTeX entries with metadata verification, then runs /bib-validate.
-
lhh666-6 Skill Insights DeckUse when you need a timestamped Codex insights report and Beamer presentation.
-
lhh666-6 Skill Latex ScaffoldUse when you need to convert a Markdown draft into a buildable LaTeX project.
-
lhh666-6 Skill Pre Submission ReportUse when you need all quality checks run before submission, producing a single dated report.
-
markfulton Skill Cos Market SweepWeekly, heavy browser lane, read only toward the world with no exception. Works the surfaces on its own watchlist through one contiguous browser phase, captures one dated observation per real change with a verbatim quote and the exact URL, refuses to report any change against a surface it has no baseline for, and writes one capped weekly page. It types nothing that changes anything, takes no action on LinkedIn ever, sends only where you released the channel, spends only where you released it, and never touches a credential.
-
markfulton Skill Cos Decision BriefWeekly, file work only, no browser at all. Reads everything the week produced, picks exactly three moves, and argues both sides of each one before the member reads a word of it, with every clause carrying a number or an observation from a file it names. It argues against its own top recommendation last, records a predicted effect and the metric that would show it so the monthly review can score it, and files each move onto the register. It sends only where you released the channel, spends only where you released it, never deploys, and never touches a credential.
-
markfulton Skill Web Weekly ReportWeekly. Scores the week from the ledgers with a source path beside every number and never writes a number it did not count in a file this run. It names exactly two things and files both as cards, the one fix worth doing next week and the one thing to stop, and it replays every learned browser flow once, read only, so a drifted selector is found on a Friday rather than on a Tuesday morning a routine needed it.
-
markfulton Skill Csat Desk StandupWeekdays, file work only, no browser at all. Reads every ledger, every queue file, and every run record since its cursor, turns the member's ticks into replied lines and closed cards, computes the first response and time to resolution clocks the Friday report is built from, folds the card inbox, re-renders the desk board, and writes the short morning brief the member opens first. It holds every outbound action unless you released the channel, and it never touches a credential.
-
markfulton Skill Csat Satisfaction ReportWeekly on a Friday, conditional browser lane. Scores the week from the ledgers with a source beside every number and an estimate nowhere, reads the review and rating movement off the member's own listing screens, replays the browser flows the weekday routines depend on, and names the one product change that would have removed the most tickets this week. It sends only where you released the channel, never posts, never resolves anything, spends only where you released it, and never touches a credential.
-
h4vzz Skill API DesignDesign RESTful APIs with proper resource modeling, HTTP method semantics, status codes, pagination, versioning, and documentation.
-
h4vzz Skill Presentation CreationCreate polished, audience-tailored presentations from outlines or documents, with support for Marp, reveal.js, Google Slides, and PPTX output formats.
-
h4vzz Skill Deep ResearchConduct in-depth, multi-step research on a given topic by decomposing queries, finding diverse sources, cross-referencing findings, and synthesizing a comprehensive report.
-
h4vzz Skill Technical WritingWrite clear, concise, and accurate technical documentation including API references, user guides, tutorials, changelogs, and architecture docs, tailored to the target audience.
Frequently asked questions
What are Docs & Writing agent skills?
Docs & writing agent skills turn AI agents into dependable technical writers: READMEs, API references, PDFs and Word documents, changelogs, and style-guide enforcement. Install one and your agent produces the same structure and tone every time it writes.
Which Docs & Writing skills are most installed?
Popular Docs & Writing skills on SkillMD right now include process-and-procedure-writing, gstack-qa-only, gstack-document-release. Rankings shift as installs change; sort this page by "Most installs" for the live list.
Do Docs & Writing skills work with Claude Code and Cursor?
Yes. Every skill here ships as a SKILL.md file, an open format that works in Claude Code, Claude.ai, Cursor, Codex, Windsurf, and 60+ other agents. Install one with npx skillmds@latest add <owner>/<name>, or copy the file into your agent's skills directory.