agentsclimarketplace

Handoff documentor

Skill AtulPurohit/Antigravity-Awesome-Skills/skills/handoff-documentor

Installable GitHub library of 300+ professional agentic skills for Claude Code, Antigravity IDE, Gemini CLI, Cursor, and Copilot. Features a custom NPX installer, 9 stack-specific bundles, validation schemas, security auditing, and an interactive catalog explorer app.

Install
npx -y skills add AtulPurohit/Antigravity-Awesome-Skills --skill handoff-documentor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Professional Handoff Documentor Expert skill. Orchestrate technical collaboration, design reviews, sprint planning, and system diagnostics.

SKILL.md

1.4 KB, 176 tokens by cl100k_base, as published. Nobody here has run it

Handoff Documentor Expert

Purpose

Manage and implement Handoff Documentor Expert requirements efficiently within enterprise applications.

Core Concepts

Detailed operational framework for Handoff Documentor Expert:

1️⃣ Overview and Strategy

Understanding boundaries, rules, and best practices for the handoff-documentor feature domain.

2️⃣ Code Implementation Reference

## Review Guidelines
- Respect coding guidelines
- Prioritize correctness and security
- Keep feedback constructive and educational

3️⃣ Checklist & Validation Rules

  • Integration validation checklist completed.
  • Code conventions and naming rules followed.
  • Strict type safety constraints verified.
  • Security standards checked.

Outputs

  1. System integration pattern definitions.
  2. Code templates and examples.
  3. Test validation checklists.

Gives 0 of the 12 instructions most agent orchestration skills give in 176 tokens

Counted across 742 of the 995 authors here whose files we hold, read 2026-08-06

  • run the full test suite after integrating changesin 53 of 742, across 20 files
  • reference existing artifacts by path or URLin 52 of 742, across 22 files
  • dispatch one agent per independent problem domainin 50 of 742, across 17 files
  • verify fixes do not conflictin 45 of 742, across 13 files
  • include a suggested skills section in the documentin 45 of 742, across 15 files
  • redact sensitive informationin 41 of 742, across 11 files
  • save to the temporary directory of the operating systemin 39 of 742, across 9 files
  • tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
  • spot check agent changes for systematic errorsin 34 of 742, across 7 files
  • write a handoff document summarising the current conversationin 31 of 742, across 6 files
  • assign each agent a specific scopein 23 of 742, across 8 files
  • provide specific scope and clear goalin 23 of 742, across 5 files

Said here and by no other author read

  • respect coding guidelines
  • prioritize correctness and security
  • keep feedback constructive and educational
  • complete the integration validation checklist
  • follow code conventions and naming rules
  • verify strict type safety constraints

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.