<Devsly/>
NotebookLM Watermark Remover
Remove the NotebookLM watermark from PDF slide exports — free, unlimited, and 100% in your browser.
View
NotebookLM Video Watermark Remover
Remove the NotebookLM watermark from every frame of your MP4 and auto-trim the end card — free and unlimited.
View
Gemini Watermark Remover
Remove the Gemini (Veo) sparkle watermark from every frame of your AI-generated MP4 — free and unlimited.
View
MCP https://devsly.io/mcp MCP Tools Best Skills API Docs

Keyboard Shortcuts

Navigation

Quick Search
⌘ / Ctrl + K
Toggle Dark Mode
⌘ / Ctrl + D
Close Dialogs
Esc

Tool Actions

Execute / Process
⌘ / Ctrl + Enter
Clear Input
⌘ / Ctrl + Shift + C
Copy Output
⌘ / Ctrl + Shift + X

Editor

Select All
⌘ / Ctrl + A
Undo
⌘ / Ctrl + Z
Redo
⌘ / Ctrl + Shift + Z

Updated today

by testdouble

han

Han: AI skills and agents for "Solo" product engineers and small teams

  • Active — Updated in the last 14 days
Works with
  • Claude

304 GitHub stars (304)

+31 in 20 days

Stars gained per day · daily snapshots since Sep 26
Stars gained per day, Sep 26 to Oct 16: +31 in total; the busiest day was Oct 15 with +11 stars.Sep 27: 0 starsSep 28: +1 starsSep 29: +1 starsSep 30: +1 starsOct 1: 0 starsOct 2: 0 starsOct 3: +1 starsOct 4: 0 starsOct 5: 0 starsOct 6: +1 starsOct 7: +1 starsOct 8: 0 starsOct 9: 0 starsOct 10: +2 starsOct 11: 0 starsOct 12: 0 starsOct 13: +1 starsOct 14: +5 starsOct 15: +11 starsOct 16: +6 stars
Stars gained between daily snapshots
PeriodNew stars
Sep 270
Sep 28+1
Sep 29+1
Sep 30+1
Oct 10
Oct 20
Oct 3+1
Oct 40
Oct 50
Oct 6+1
Oct 7+1
Oct 80
Oct 90
Oct 10+2
Oct 110
Oct 120
Oct 13+1
Oct 14+5
Oct 15+11
Oct 16+6
  • 30 skills (30 skills found in its SKILL.md files)
  • 24 forks (24 forks)
  • Today last update (Last updated today)

Install

Skills CLI

npx skills add testdouble/han

Asks which skills and agents to install. Just one: npx skills add testdouble/han --skill han-release — add -g for every project.

Claude Code

git clone https://github.com/testdouble/hancp -r "han/.claude/skills/han-release" ~/.claude/skills/

Copies the han-release skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add testdouble/han

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

In the author's own words, from each skill's SKILL.md — showing the first 30 of 55 files.

  • han-release

    Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when releasing, cutting a release, shipping a new Han version, publishing release notes, or…

    .claude/skills/han-release/SKILL.md on GitHub (opens in a new tab)
  • han-update-documentation

    Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing, syncing, auditing, or verifying Han's docs after changing skills, agents, referen…

    .claude/skills/han-update-documentation/SKILL.md on GitHub (opens in a new tab)
  • code-overview-to-confluence

    Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Use when the user wants code or a PR explained, oriented, or made sense of AND the overview posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not produce the overview to a loc…

    han-atlassian/skills/code-overview-to-confluence/SKILL.md on GitHub (opens in a new tab)
  • investigate-to-confluence

    Runs an evidence-based investigation of a bug, failure, or unexpected behavior with investigate and publishes the resulting investigation report to a user-specified Confluence location. Use when the user wants something debugged, diagnosed, or root-caused AND the findings posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not investigate to a local file only —…

    han-atlassian/skills/investigate-to-confluence/SKILL.md on GitHub (opens in a new tab)
  • markdown-to-confluence

    Publishes a local Markdown file to a user-specified Confluence location, creating a new page or updating an existing one through the Atlassian MCP server. Use when the user wants to post, publish, push, or sync a Markdown file to a Confluence space or page. Requires a configured Atlassian MCP server. Does not write or generate the Markdown itself — point it at an existing file, or use project-doc…

    han-atlassian/skills/markdown-to-confluence/SKILL.md on GitHub (opens in a new tab)
  • plan-a-feature-to-confluence

    Builds a feature specification from scratch with plan-a-feature and publishes it to a user-specified Confluence location, posting the spec as a parent page and each companion artifact (decision log, team findings, technical notes) as a child page beneath it. Use when the user wants a new feature planned, designed, scoped, or specified AND posted to a Confluence space or page. Requires a configure…

    han-atlassian/skills/plan-a-feature-to-confluence/SKILL.md on GitHub (opens in a new tab)
  • project-documentation-to-confluence

    Creates or updates project documentation for a feature, system, or component and publishes it to a user-specified Confluence location. Use when the user wants feature or system documentation written to Confluence, posted to a Confluence space or page, or synced to a Confluence location. Requires a configured Atlassian MCP server. Does not document to local files only — use project-documentation f…

    han-atlassian/skills/project-documentation-to-confluence/SKILL.md on GitHub (opens in a new tab)
  • work-items-to-jira

    Break a work-items.md file (produced by /plan-work-items) into independently-grabbable Jira tickets, one per slice, in a single Jira project. Use when you want to turn a work-items file into Jira tickets, publish work items as Jira issues, or create implementation tickets that can be worked on and tracked in Jira. Requires a configured Atlassian MCP server. Does not produce the work-items file it…

    han-atlassian/skills/work-items-to-jira/SKILL.md on GitHub (opens in a new tab)
  • architectural-analysis

    "Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific…

    han-coding/skills/architectural-analysis/SKILL.md on GitHub (opens in a new tab)
  • automated-test-planning

    Produce a standalone test plan by analyzing code for test coverage gaps and edge cases. Use when you need to create, generate, or draft a test plan for a branch, need to analyze test coverage, or need to identify what tests to write for specific files or directories. Does not produce a plain-language plan for a person to run tests by hand — use manual-test-planning for that. Does not write test c…

    han-coding/skills/automated-test-planning/SKILL.md on GitHub (opens in a new tab)
  • code-overview

    Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or goal it serves for the business or a user), and from there what it does, how it flows, and where to start — so you can get up to speed before working on or reviewing it. Use when you want to understand, get oriented in, make sense of, explain, or…

    han-coding/skills/code-overview/SKILL.md on GitHub (opens in a new tab)
  • code-review

    'Run a comprehensive code review on local source files. Use this skill when the user asks to review, audit, inspect, evaluate, or check code, even if they never use the word "review." Does not post comments to GitHub pull requests — use post-code-review-to-pr for that. Does not analyze architectural structure or module boundaries — use architectural-analysis for that. Does not explain code or a P…

    han-coding/skills/code-review/SKILL.md on GitHub (opens in a new tab)
  • code-walkthrough

    Walks a person through code changes one step at a time in conversation, starting at the entry point and following the flow that changes, showing a small chunk per step and explaining it in plain language. Defaults to the current branch's changes, and walks the code from the perspective of any context provided instead — a file, directory, symbol, pull request, plan, or ticket. Use when someone wan…

    han-coding/skills/code-walkthrough/SKILL.md on GitHub (opens in a new tab)
  • coding-standard

    Creates and updates coding standards, conventions, rules, and guidelines for the current project. Use when creating new standards from scratch, converting existing documents into coding standards, or updating existing standards. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not write feature or system documentation — use project-documentation fo…

    han-coding/skills/coding-standard/SKILL.md on GitHub (opens in a new tab)
  • design-an-api

    Designs the contract for an API change inside one codebase — a component's props, a function surface, URL or query parameters, an event payload, or a module boundary — through a discovery pass, an options document with one recommendation, a question round, and an adversarial validation round, with every element of the contract justified from one stated goal. Use when you want to design, shape, de…

    han-coding/skills/design-an-api/SKILL.md on GitHub (opens in a new tab)
  • investigate

    Evidence-based investigation of issues, bugs, API calls, integrations, and other aspects of software development that need a deep dive to find the root cause and solutions. Use when you need to debug, troubleshoot, diagnose, or figure out why something is broken. Does not review code for quality or style — use code-review for auditing changes or post-code-review-to-pr for posting review feedback…

    han-coding/skills/investigate/SKILL.md on GitHub (opens in a new tab)
  • manual-test-planning

    Produce a plain-language manual test plan from the context supplied to it — an executive summary, a high-level list of named tests, and a detail section per test with the steps a person follows by hand and the outcomes they should expect. Use when you want to create, draft, generate, or outline a manual test plan, manual QA steps, hands-on verification steps, or an acceptance walkthrough for a fe…

    han-coding/skills/manual-test-planning/SKILL.md on GitHub (opens in a new tab)
  • refactor

    Restructure existing code without changing its behavior, through a test-gated refactoring loop: a named target, a green suite over that target before any edit, a planned sequence of small named refactorings, and the full suite re-run after every step. Use when the user wants to refactor, restructure, clean up, simplify, or improve the design of existing code, or to apply refactoring recommendatio…

    han-coding/skills/refactor/SKILL.md on GitHub (opens in a new tab)
  • tdd

    Write code through a disciplined, BDD-framed Test-Driven Development loop: build a behavior test list, then drive each behavior through red-green-refactor with an enforced observed-failure gate. Use when the user wants to implement, build, or write code test-first, "do TDD", follow "red-green-refactor", drive code from tests, choose the next test by the Transformation Priority Premise (TPP) or ZO…

    han-coding/skills/tdd/SKILL.md on GitHub (opens in a new tab)
  • edit-for-readability

    Applies Han's shared Human-Readable Output Standard to a target you already have — a file on disk, text pasted into the prompt, or a draft already produced in the conversation — by dispatching the readability-editor to rewrite its prose so the main point comes first, headings are descriptive, each paragraph carries one idea, and sentences stay short and active, while preserving every fact. Use wh…

    han-communication/skills/edit-for-readability/SKILL.md on GitHub (opens in a new tab)
  • explanation-guidance

    Surfaces Han's shared standard for explaining technical work to a reader who will not implement it into the calling skill's own context, so the caller writes its escalations, confirmation turns, and stops as a concrete outcome the reader could observe rather than as a mechanism. Use when a skill is about to ask a person a question, stop for an input, or explain a technical consequence to someone…

    han-communication/skills/explanation-guidance/SKILL.md on GitHub (opens in a new tab)
  • readability-guidance

    Surfaces Han's shared Human-Readable Output Standard — the readability rule and the writing-voice profile — into the calling skill's own context, so the caller drafts in voice and runs its self-check against the current standard sourced from one canonical copy. Use when a prose-producing skill needs the shared readability standard available in context before it drafts. Governs the shape of a writ…

    han-communication/skills/readability-guidance/SKILL.md on GitHub (opens in a new tab)
  • pairing

    Build work collaboratively in reviewable pieces, handing each piece back for review before starting the next, so the person stays in the lead and steers while the work happens instead of reviewing a finished result. Use when someone says to pair with them on something, asks to collaborate rather than direct, wants to review as it goes, or wants to guide the work piece by piece — on code, on a des…

    han-core/skills/pairing/SKILL.md on GitHub (opens in a new tab)
  • project-discovery

    Discovers the core attributes of the current code repository and its projects — languages, frameworks, tooling, and where things live — and writes a concise reference section directly into the project's AGENTS.md or CLAUDE.md for other skills, agents, and hooks to consume. Use when scanning, analyzing, or detecting the project's technology stack, build tools, or repository structure. Does not cre…

    han-core/skills/project-discovery/SKILL.md on GitHub (opens in a new tab)
  • ddd-analysis

    "Analyzes an existing codebase using strategic Domain-Driven Design to discover bounded contexts, surface ubiquitous language and semantic collisions, find places where code boundaries diverge from domain boundaries, and produce an evidence-backed domain and context map. Use when the goal is DDD-specific: bounded context discovery, ubiquitous language analysis, domain model discovery, or mapping…

    han-ddd/skills/ddd-analysis/SKILL.md on GitHub (opens in a new tab)
  • architectural-decision-record

    Create, extract, or convert an ADR (architectural decision record) using the ADR template. Use when creating new ADRs, extracting an ADR from existing documentation, converting a document into an ADR, recording an architecture or design decision, or updating the status of an existing ADR. Does not create or update enforceable coding standards or conventions — use coding-standard for that. Does no…

    han-documentation/skills/architectural-decision-record/SKILL.md on GitHub (opens in a new tab)
  • project-documentation

    Creates and maintains project documentation for features, systems, and components. Use when documenting how a feature, system, or component works — including writing, updating, or organizing docs. Does not scan or detect the project's technology stack — use project-discovery for repository analysis and config detection. Does not create architectural decision records — use architectural-decision-r…

    han-documentation/skills/project-documentation/SKILL.md on GitHub (opens in a new tab)
  • runbook

    Create or update a runbook for an operational scenario — an incident an alert fires for, a recurring scheduled task, or a known failure mode on a live service — using a consistent template. Use when writing, drafting, authoring, or updating a runbook for an alert, incident, on-call procedure, scheduled maintenance, or operational SOP. Applies a YAGNI preflight requiring the scenario to be real be…

    han-documentation/skills/runbook/SKILL.md on GitHub (opens in a new tab)
  • han-feedback

    Capture structured feedback on the Han skills and agents used in the current session and optionally post it as a GitHub issue to testdouble/han. Use at the end of any session where one or more han-* skills or agents ran, to rate a run, log what worked and what didn't, or submit observations for maintainers. Does not review code, investigate bugs, or research options; use code-review, investigate,…

    han-feedback/skills/han-feedback/SKILL.md on GitHub (opens in a new tab)
  • post-code-review-to-pr

    Run a full pull request review and post review comments directly to the current branch's GitHub PR. Requires the gh CLI to be installed and a PR to already exist for the current branch. Use when you want review feedback posted to GitHub as PR comments. For local code review without posting to GitHub, use code-review instead. Does not write or update PR descriptions — use update-pr-description for…

    han-github/skills/post-code-review-to-pr/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.