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
agony1997/TouchFish-Skills/plugins/git-nanny/skills/git-nanny Skill
0★ repoGit 全方位專家:涵蓋 Commit 訊息生成、Pull Request 建立與審查、分支策略管理、版本發布與 Changelog。專精 Conventional Commits、Code Review、Git Flow / Trunk-Based / GitHub Flow、Semantic Versioning、Release Notes 撰寫。關鍵字: commit, pull request, PR, branch, release, changelog, git flow, trunk-based, github flow, semantic versioning, conventional commits, code review, git tag, 提交, 分支, 版本發布, 合併請求, 程式碼審查, 更新日誌, 版本號, semver, hotfix, 緊急修復, merge, 合併, 合併策略, rebase, squash, tag, 標籤
The same file is in 2 other repositories
ArthurZakirov/SystemSmith/skills/living-artifacts Skill
0★ repoApply when producing any markdown artifact for someone else (or future-you) to read — READMEs, analysis documents, Confluence pages, status reports, troubleshooting write-ups, skill content, conversation summaries, ticket descriptions, post-mortems, snapshots of system state, or any document that contains concrete current-state values. Defines the "snapshot + reproducer" rule (every static value must be paired with the command/query/script that regenerates it), the single-source-of-truth rule (reference canonical homes instead of duplicating values), and fact-vs-assumption marking. Trigger keywords include writing or producing or creating or drafting a README, analysis, Confluence page, status update, summary, snapshot, current state, documenting data, posting findings, file tree, port number, version number, table count, or any concrete value that may drift over time.
ArthurZakirov/SystemSmith/skills/messaging-framework Skill
0★ repoCore principles for technical communication such as commits, PR descriptions, branch names, and technical documentation. Use when writing or refining engineering-facing messaging and when other skills need a shared communication baseline.
AI-Driven-School/aiki/.claude/skills/requirements Skill
0★ repoGenerate a requirements document with user stories, acceptance criteria, and constraints. Use when defining features, writing specs, or running /requirements before implementation.
Topurrra/claude-plugins/plugins/craft/skills/mythos Skill
no license0★ repoUse for every response, document, plan, comment, commit, UI copy, or artifact to make output token-lean and mythic in density: the same information in fewer tokens, with more resonance. The always-on writing layer that runs underneath every task in the Craft library.
Documentation and knowledge capture
Topurrra/claude-plugins/plugins/foundational-skills/skills/documentation-and-knowledge-capture Skill
no license0★ repoUse when work will be used or maintained by someone else or revisited later, to capture the why and how to use it without over-documenting.
ArthurZakirov/ProofStack/skills/profile_readme_positioning Skill
no license0★ repoWrite GitHub profile bios, project README intros, and technical-lab positioning that honestly distinguishes personal experiments from professional experience while making the builder identity clear.
latuconsinafr/claude-code-config/skills/test-cases Skill
no license0★ repoUse when you need to document E2E test cases for a feature or bug fix that can't be covered by unit or integration tests alone. Auto-detects ticket from branch name. Reuses codebase context from /plan if already run; falls back to git diff + explorer when invoked standalone. Outputs to a markdown file by default.
manu-brighter/claude-code-kit/plugins/dev-workflow/skills/project-refresh Skill
0★ repoAudits the project's documentation-adjacent artifacts — README, project brief, CHANGELOG, further docs (docs/, wiki exports), deployment info (compose files, reverse-proxy and orchestration config docs), and i18n/translation files — against the actual current state of the codebase, and fixes whatever has drifted out of date. Also translates new/changed UI strings directly into every existing locale file. EXPLICIT-INVOCATION ONLY: use this skill solely when the user invokes it by name or runs it as a slash command. Do NOT auto-trigger or infer it from generic requests like "update the docs", "sync the README", "add translations", or "bring the project up to date" — for those, do the work directly or ask which parts they mean. This skill is strictly opt-in, and distinct from `full-project-rework` (which is a heavy code-quality overhaul with its own docs-sync step) — this one is documentation, deployment-info and i18n only: lightweight, no branch, no multi-phase pipeline.
thinkyou0714/github-flow-kit/release-notes Skill
0★ repoGenerate human-readable release notes from git history and merged PRs. Creates two versions: user-facing (what's new in plain language) and developer-facing (conventional changelog format). Publishes as a GitHub Release draft with auto-suggested semver bump. Use when you're preparing a release, want to document what changed since the last tag, or need to write CHANGELOG entries. Triggers on: "リリースノート", "changelog", "release notes", "何が変わった", "バージョンアップ", "release-notes". DO NOT USE FOR: creating a new git tag, deploying to production.
thinkyou0714/github-flow-kit/repo-tour Skill
0★ repoGenerate a comprehensive onboarding guide for any codebase. Produces a REPO_TOUR.md with a 30-second summary, annotated directory tree, Mermaid architecture diagram, key files list, and "where to look for X" quick-reference. Use when you're new to a codebase, onboarding a team member, or need to document the overall structure. Also useful after a major refactor to update understanding. Triggers on: "このリポジトリを説明して", "コードベースを理解したい", "repo tour", "architecture overview", "repo-tour", "onboarding", "どこから読めばいい". DO NOT USE FOR: editing code, fixing bugs, or creating documentation beyond structure.
Ephemeral container file detection
Ed3Design/ed3design-skill-bundles/async-forensik/skills/ephemeral-container-file-detection Skill
0★ repoUse when designing or auditing Docker-based deployments BEFORE writing implementation plans that rely on files persisting across container rebuilds. Trigger on phrases like "volume mount for X", "why are the files gone", "container rebuild deleted the models", "model_path points to a file that's not there", "phantom registry in DB", "inference fails with FileNotFoundError", "before Claude build — are the prerequisites in place", "pre-flight deployment audit", "writing-plans for a Docker feature with persistent data". Detection-Pattern in 4 steps: docker inspect Mounts → ls container dir → stat birth-time → grep dump/save calls in code → if code writes but the mount list does NOT include the path → ephemeral, pre-flight STOP for the feature phase. Do NOT load for non-Docker deployments (systemd services, Kubernetes StatefulSets — different model), for read-only containers without write paths, for single-file apps without a storage layer. The maxim "read logs/code/DB first" applied to deployment prerequisites.
Reporting artefact detection before claiming anomaly
Ed3Design/ed3design-skill-bundles/async-forensik/skills/reporting-artefact-detection-before-claiming-anomaly Skill
0★ repoUse when observing a "surprising anomaly" in backtest output, SQL query result, multi-run-eval-report, ML-model-performance-table, or any reporting-layer artefact suggesting a system bug, market outlier, methodological problem, or drift. Before treating the anomaly as real and dispatching forensic resources, run a 3-step triage: (1) NULL-handling check — are NULLs in numerator/denominator mishandled, was IS NOT NULL omitted? (2) Cross-window / unique-ID check — do overlapping sub-windows / joins count rows multiple times? (3) Methodology-consistency check vs previous report — was the same SQL replicated exactly? Trigger phrases like "why is WR suddenly so low", "I don't understand this anomaly", "24h drift", "baseline has changed", "backtest gives different numbers today than yesterday". Do NOT load for confirmed-real anomalies, first-time-setup-debugging without baseline, code-bugs in the algorithm itself, or UI rendering bugs.
Plan execution state drift precheck
Ed3Design/ed3design-skill-bundles/planning-disciplines/skills/plan-execution-state-drift-precheck Skill
0★ repoUse before executing any superpowers/gsd-style implementation plan (`docs/superpowers/plans/*.md`, `.planning/PLAN.md`, `roadmap-phase-*.md`) whose plan-file was written in a previous session — to detect whether tasks have already been implemented (in a parallel session, by a different agent, or by the user) before re-executing them. Trigger on phrases like "start plan execution", "apply executing-plans skill", "gsd-execute-phase", "execute phase", "plan file is from yesterday/last week", "plan written earlier, now executing". Without `git log <base>..HEAD` precheck, completed tasks can be re-implemented inline, wasting significant time. Do NOT load for plans written in the SAME session (no drift possible), plans without git-tracked code targets (pure-documentation phases), or when the user explicitly states "the codebase is at the pre-plan state".
Explicit unknown counter vs coalesce mask
Ed3Design/ed3design-skill-bundles/schema-discipline/skills/explicit-unknown-counter-vs-coalesce-mask Skill
0★ repoUse when writing aggregating SQL (SUM/AVG/COUNT) or Python-side aggregates over a NULL-able column where NULL means "data not present / not backfilled / unknown" (NOT "intentionally zero"). The naive `COALESCE(SUM(x), 0)` or `df.col.fillna(0).sum()` masks NULL-rows silently — drift goes undetected for weeks. Instead, ALWAYS pair the aggregate with an explicit `count(*) FILTER (WHERE col IS NULL)` Counter (Postgres) or `df.col.isna().sum()` (pandas), surfaced in the same response shape. Trigger phrases like "aggregate PnL", "monthly sum", "trade statistics", "NULL handling", "summary report with NULLable column", "why doesn't the aggregate match the memory", "drift in reporting". Do NOT load for columns where NULL is semantically zero (intentional NOT-NULL-DEFAULT-0 design — then COALESCE is correct), for non-aggregating queries (single-row SELECTs), or for transient runtime calculations where NULL means "in-flight" rather than "unknown".
Schema use case mismatch detection
Ed3Design/ed3design-skill-bundles/schema-discipline/skills/schema-use-case-mismatch-detection Skill
0★ repoUse when a user reports "field X is always NULL in table Y despite active code" or "data missing from a table that's actively being written to" — BEFORE jumping to "fix the bug, set the field". Iron-Law: when a single DB-table has ≥2 writer-paths with different semantics (per-trade vs per-portfolio, legacy vs new pipeline), the field-NULL-symptom is often NOT a bug but a schema-use-case-mismatch — the active writer simply lacks the semantics to produce that field. A "fix" without this check would patch the writer to set a value that doesn't exist semantically. Trigger on phrases like "verdict is always NULL", "field X always missing", "this column is never populated", "INSERT list incomplete", "data not appearing despite job running", "two write-paths same table different semantics". Do NOT load for ALTER-TABLE-missing-column, permission issues, connection issues, or first-implementation of a feature.
Schema verify via information schema
Ed3Design/ed3design-skill-bundles/schema-discipline/skills/schema-verify-via-information-schema Skill
0★ repoUse when about to write or execute SQL against a PostgreSQL/TimescaleDB table whose exact schema (column names, types, deprecated-vs-active-variant) is not 100% certain from current context — especially in forensic debugging where multiple tables have similar names (`ohlcv_1d` vs `ohlcv_1d_hist`, `users` vs `users_v2`) or column names have shifted over time. Iron-Law: `SELECT column_name, data_type FROM information_schema.columns WHERE table_name=$1 ORDER BY ordinal_position` is the cheapest 30-second insurance against UndefinedColumn, false-positive-empty-result, and wrong-table-queried. Trigger on phrases like "writing a query against table X", "UndefinedColumn", "column X does not exist", "verify DB schema", "I think the column is called Y", "before any forensic query". Do NOT load for ORM-mediated queries (SQLAlchemy/Django catch drift at model-load), first-time-schema-design, catalog-queries on information_schema itself, or connection issues.
Docx tab position extraction for layout replication
Ed3Design/ed3design-skill-bundles/token-savers/skills/docx-tab-position-extraction-for-layout-replication Skill
0★ repoUse when replicating a document layout (business letter, invoice, contract) from an existing Word `.docx` file in HTML/CSS/PDF/Print-CSS — a user provides a previous Word document as "make my web letter look like THIS" and you need precise tab-stop / margin / indentation positions. STOP and extract the actual measurements from the DOCX XML before writing CSS by eye. DOCX is a ZIP-archive containing `word/document.xml`; tab stops live in `<w:tab w:pos="6803" />` where `w:pos` is in **twips** (1/1440 inch); convert with `mm = twips ÷ 1440 × 25.4`. The same applies to margins (`<w:pgMar>`), indentation (`<w:ind>`), and column widths (`<w:gridCol>`). Trigger on phrases like "replicate the layout from my old Word letter", "make the layout like the DOCX", "convert twips to mm", "measure the layout, don't estimate it". Do NOT load for designing a layout from scratch, for `.doc` binary legacy format (convert via LibreOffice headless first), for `.docx` where layout is irrelevant, or when the reference is a PDF.
ClydeShen/harness-skill/skills/productivity/write-harness-skill Skill
0★ repoCreate new harness-compatible agent skills with proper structure, progressive disclosure, and bundled resources — includes harness-specific checklist (token budget, setup-harness-skills reference, AI footer, creation gates). Use when user wants to create, write, or build a new skill.
richardkmichael/claude-rodin/skills/matlab-docs Skill
0★ repoLook up MATLAB / MathWorks docs by function name, mathworks.com URL, or local help-HTML path. Use in preference to WebFetch for any mathworks.com URL — WebFetch gets HTTP 403 from the MathWorks WAF; this skill uses curl. Triggers on "matlab docs", "mathworks docs", a pasted mathworks.com docs URL, or any time you need to consult MATLAB documentation.
chenwei791129/agent-skills/hermes-skills/superpowers/writing-plans Skill
0★ repoUse when you have a spec or requirements for a multi-step task, before touching code
chenwei791129/agent-skills/skills/facebook-scraper Skill
0★ repoScrape posts (text, images, top-level comments) from a Facebook group or fan page and output a Markdown report. Use when: the user wants to scrape, back up, or collect FB group/page post content and comments. Trigger on: facebook group, fan page, post scrape, fb group/page scraper.
chenwei791129/agent-skills/skills/powershell-style-guide Skill
0★ repoReview and write PowerShell code following community style guide and best practices (based on PoshCode/PowerShellPracticeAndStyle). Use when writing new PowerShell scripts, functions, or modules (.ps1, .psm1, .psd1), reviewing PowerShell code for style compliance, refactoring PowerShell code, or any task involving PowerShell scripting where code quality matters.
chenwei791129/agent-skills/skills/shell-style-guide Skill
0★ repoReview shell/bash code for adherence to Google Shell Style Guide. Use when the user requests a code review of shell scripts (.sh, .bash), writing new shell scripts, fixing shell script issues, or checking shell code against style guidelines. Trigger phrases include: review this shell script, check shell style, write a bash script, review my shell code, or any task involving shell/bash scripting where code quality and consistency matter.
agency-shift/agency-shift-skills/agency-deliverable-handoff Skill
0★ repoPackage a finished deliverable for client handoff — produces the handoff message, the QA checklist that proves it's done, the asset link manifest, and the next-action ask. Use whenever the user says "ship this", "hand this over", "send to client", "deliverable is ready", or pastes a list of done items + asset URLs and asks for the handoff message. Do NOT use this skill for weekly status updates (use agency-weekly-report instead) or for internal team handoffs between two agency staff.
agency-shift/agency-shift-skills/agency-weekly-report Skill
0★ repoGenerate a polished, client-ready weekly status report for a marketing, content, or creator agency client. Use whenever the user asks to "build the weekly report", "write the Friday update", "summarize the week for [client name]", or pastes raw work logs / Linear / Notion exports and asks for a client-facing summary. Do NOT use this skill for internal team retros or for individual employee performance reviews — it is specifically scoped to outbound client communication.
Bbar0n234/llm-engineer-skills/skills/skill-writing Skill
0★ repoПомогает создавать и структурировать скиллы для Claude Code. Используй когда нужно написать, создать, организовать или отрефакторить скилл. Skill writing, skill creation, create skill, write skill, new skill, author skill.
mi4646/my-skills/skills/weekly-report Skill
no license0★ repo生成开发周报,根据 git commit 历史归纳本周/上周的工作成果。当用户提到"周报"、"工作总结"、"本周工作"、"上周工作"、"weekly report"、"写周报"、"生成本周总结"时触发此技能,即使用户没有明确说"周报"但表达了回顾近期工作的意图也应触发。
gigayaya/gigachang-skills/skills/markdown-to-html-article Skill
0★ repoUse when about to present long or complex AI-generated markdown to the user — typically >150 lines, >5 H2 sections, or content like code reviews, implementation plans, specs, research reports. Also use when the user explicitly asks to convert a markdown source into a readable HTML article. Produces a single self-contained HTML article (hero image, article lede, magazine typography, pull quotes, quiet asides, syntax-highlighted code, inline concept tooltips, dark mode) saved to ./claude-articles/. Zero install — the renderer is stdlib-only Python. Skip for short, simple, or plain-text content where the conversion cost outweighs the reader's time savings.
gigayaya/gigachang-skills/skills/scope-research Skill
0★ repoUse when the user explicitly asks to research the scope of a requirement or proposed change against the current codebase — e.g. "research the scope of this requirement", "what would adding X touch in this codebase", "do scope research on this spec", "/scope-research". Surveys the codebase to surface concrete facts about which files/areas a change would touch and the relevant facts about each touchpoint (callers, prior similar changes, current test state, conventions in use, data/interface contracts), with an honest LOC range per touchpoint. Presents facts neutrally — does not assign t-shirt sizes, time estimates, or risk ratings. When unsure about something material, asks the user clarifying questions before writing the report. Manual-trigger only — never auto-invoke. Skip for trivial single-file or one-line changes where research adds no value.
bogheorghiu/ex-cog-dev/research-toolkit/skills/youtube-research Skill
0★ repoWhat do practitioners actually DO (not just document)? Methodology for extracting practitioner knowledge from YouTube video transcripts. Use when (1) researching how people actually use a technology, (2) seeking practitioner insights beyond documentation, (3) looking for tips, patterns, or workflows from creators, (4) building a research corpus from video content.
chienchuanw/chuan-skills/plugins/dev/skills/health-audit Skill
no license0★ repoManually-triggered comprehensive codebase health audit covering security, architecture, documentation drift, dead code, and test coverage gaps. Produces a ranked markdown report, files prioritized GitHub issues, and proposes (but never autonomously opens) auto-fix PRs for trivial safe changes. Use when the user wants to audit, scan, review the health of, do a security check on, find dead code in, check doc drift in, or get a backlog of improvement issues for a repository — e.g. "/health-audit", "audit this repo", "do a full health check", "scan for issues to file", "check what's rotting in here". Scoped to a whole repository: not for ad-hoc bug hunts on a single file (use feature-dev:code-reviewer), and not for scoring an individual skill's quality (use skill-benchmark).
chienchuanw/chuan-skills/plugins/docs/skills/readme Skill
no license0★ repoWrite a new README.md or improve an existing one. Use when the user asks to create, update, or improve a README, or wants to document a project and no other documentation skill is more specific.
chienchuanw/chuan-skills/plugins/git/skills/branch-report Skill
no license0★ repoGenerates a branch-vs-default comparison report with plain-language explanations and senior dev review. Use when the user asks to summarize, compare, review, or explain branch changes, or wants a PR summary before merging. Read-only: it produces a report to read — it does not push the branch or open/update the PR (for that use gh-pr).
chienchuanw/chuan-skills/plugins/git/skills/gh-archive Skill
no license0★ repoCapture the current state of a project by updating documentation at the end of a development session. Invokes the readme skill to refresh README.md and the planning-with-files skill to record project status in a doc/ or docs/ directory. Use after merging a PR, finishing a feature, wrapping up a coding session, or any time the user wants to snapshot where the project stands — even implicit phrases like "archive this", "wrap up the session", "document current status", "update project docs", "snapshot this repo", or "I'm done for today". Also use when the user says "end of session" or asks to prepare documentation before stepping away from a project.
chienchuanw/chuan-skills/plugins/skill-optimize/skills/gotcha-capture Skill
no license0★ repoUse when the user encountered a problem, bug, edge case, or frustration with an existing skill and wants to save that knowledge into the skill's file. Trigger phrases include "add a gotcha", "document this pitfall", "capture lessons learned", "record edge cases", "pull out what went wrong", but also trigger when the user simply describes something that went wrong or was painful with a named skill (like readme, commit-msg, seo-meta, branch-report, gh-pr) and asks to update it, save it, or make sure it doesn't happen again. This skill mines conversation history for failure knowledge and writes it into the skill's Gotchas section. Do NOT use for creating new skills, adding features to skills, or changing how skills behave — only for documenting what went wrong.
chienchuanw/chuan-skills/plugins/skill-optimize/skills/skill-benchmark Skill
no license0★ repoBenchmark a skill's quality by analyzing its structure, description, documentation, and live value-add from multiple perspectives using parallel agents. Use when the user asks to benchmark, evaluate, score, audit, assess, or rate a skill's quality, or wants to know if a skill is worth keeping vs. deprecating. Also trigger when the user asks "how good is this skill", "is this skill useful", "should I keep this skill", "review skill quality", or wants a thorough multi-dimensional analysis of a skill before deciding whether to improve or remove it. Scoped to one skill: for a whole-repository health/security audit use health-audit, not this. Takes a skill name as argument (e.g., /skill-benchmark readme). Produces a scored report with actionable improvement suggestions. Do NOT use for creating new skills, editing skill code, or capturing gotchas — those are different workflows.
pacho-h/ssep/skills/reviewing-spec-and-policy Skill
0★ repoReviews product specs, requirements docs, RFCs, PRDs, and policy documents from text, markdown, or Figma. Use for completeness, consistency, edge-case coverage, ambiguity, policy conflicts, or compliance gaps. Triggers on "이 기획서 검토해줘", "스펙 리뷰", "정책 검토", "review this PRD", "is this complete?", "이 기획대로 구현하면 빠진게 뭐가 있을까", "스펙 갭", "요구사항 누락", or whenever a Figma URL is shared in a planning context. Triggers even when the requirement reads as a single concise sentence (e.g. "X should default to inactive and be activatable from detail"); concise requirements hide unstated questions about default values for existing data, role/permission interactions, and state-transition edges that a structured audit surfaces in minutes. Reads sources, runs a multi-dimensional review, returns a prioritized gap report. Distinct from brainstorming (generates new designs) and reviewing-design-fidelity (compares impl vs design); this audits an existing artifact.
zxt6991-source/fitness-agent/skills/fitness-agent Skill
no license0★ repoOperate the local Fitness Agent CLI for Strava and Obsidian workflows. Use when Codex needs to authenticate with Strava, list or fetch Strava activities, export workout data as Obsidian-compatible Markdown, configure a local Obsidian vault path, or write/sync workout notes into a vault from the local fitness-agent project.
quanpersie2001/pulse/skills/refresh-project-docs Skill
no license0★ repoUse when repository documentation is stale and the user asks to refresh docs to match the current codebase and workflows.
quanpersie2001/pulse/skills/writing-pulse-skills Skill
no license0★ repoUse when creating a new pulse skill, editing an existing pulse skill, or verifying a skill works under pressure before deploying. Use when you need an agent skill to be bulletproof against rationalization. Do NOT use for project-specific AGENTS.md conventions or one-off solutions.
JamesPrial/skills/skills/doc-coauthoring Skill
no license0★ repoGuide 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
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/article-writing Skill
no license0★ repoWrite articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
The same file is in 4 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/awesome-claude-skills/changelog-generator Skill
no license0★ repoAutomatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
The same file is in 14 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/awesome-claude-skills/composio-skills/writer-automation Skill
no license0★ repoAutomate Writer tasks via Rube MCP (Composio). Always search tools first for current schemas.
The same file is in 5 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/awesome-claude-skills/content-research-writer Skill
no license0★ repoAssists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
The same file is in 15 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/brand-voice Skill
no license0★ repoBuild a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
The same file is in 3 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/changelog-generator Skill
no license0★ repoAutomatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
The same file is in 14 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/composio-skills/writer-automation Skill
no license0★ repoAutomate Writer tasks via Rube MCP (Composio). Always search tools first for current schemas.
The same file is in 5 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/content-research-writer Skill
no license0★ repoAssists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
The same file is in 15 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/documentation-lookup Skill
no license0★ repoUse up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
The same file is in 4 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/nutrient-document-processing Skill
no license0★ repoProcess, convert, OCR, extract, redact, sign, and fill documents using the Nutrient DWS API. Works with PDFs, DOCX, XLSX, PPTX, HTML, and images.
The same file is in 5 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/superpowers/skills/writing-plans Skill
no license0★ repoUse when you have a spec or requirements for a multi-step task, before touching code
The same file is in 12 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/superpowers/skills/writing-skills Skill
no license0★ repoUse when creating new skills, editing existing skills, or verifying skills work before deployment
The same file is in 7 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/visa-doc-translate Skill
no license0★ repoTranslate visa application documents (images) to English and create a bilingual PDF with original and translation
The same file is in 8 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/zeoel-codebase-knowledge Skill
no license0★ repoUse this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
The same file is in 1 other repository
goharabbas321/zeoel-framework/all-skills/article-writing Skill
no license0★ repoWrite articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
The same file is in 4 other repositories
goharabbas321/zeoel-framework/all-skills/awesome-claude-skills/changelog-generator Skill
no license0★ repoAutomatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
The same file is in 14 other repositories
goharabbas321/zeoel-framework/all-skills/awesome-claude-skills/composio-skills/writer-automation Skill
no license0★ repoAutomate Writer tasks via Rube MCP (Composio). Always search tools first for current schemas.
The same file is in 5 other repositories
goharabbas321/zeoel-framework/all-skills/awesome-claude-skills/content-research-writer Skill
no license0★ repoAssists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
The same file is in 15 other repositories