How do I install the Oo Docsend 2 PDF skill?

Run npx skillmds@latest add oomol-lab/oo-docsend-2-pdf in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Oo Docsend 2 PDF safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Oo Docsend 2 PDF?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Oo Docsend 2 PDF free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Oo Docsend 2 PDF?

oomol-lab (@oomol-lab) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Oo Docsend 2 PDF by oomol-lab — Agent Skill

Name: Oo Docsend 2 PDF
Author: oomol-lab

File contents

Docsend2pdf

Operate Docsend2pdf through your OOMOL-connected account. This skill calls the docsend_2_pdf connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Docsend2pdf needs no account connection. Assume the oo CLI is installed and signed in. Do not run oo auth login proactively — just run the action. Fall back to First-time setup only when a command actually fails.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "docsend_2_pdf" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "docsend_2_pdf" --action "<action_name>" --data '<json>' --json

--data takes a JSON object string or @path/to/file.json; omit it to send {}.
The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

convert — Convert a DocSend document URL to PDF and return JSON-safe download metadata.

Safety

Untagged actions are reads (get / list / search) — safe to run directly.
Actions tagged [write] change Docsend2pdf state — confirm the exact payload and effect with the user before running.
Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

Not signed in / authentication error — sign in to your OOMOL account once:
```
oo auth login
```
HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

Docsend2pdf homepage: https://docsend2pdf.com

---name: oo-docsend-2-pdfdescription: Docsend2pdf (docsend2pdf.com). Use this skill for ANY Docsend2pdf request — searching and reading data. Whenever a task involves Docsend2pdf, use this skill instead of calling the API directly.---# Docsend2pdfOperate **Docsend2pdf** through your OOMOL-connected account. This skill calls the `docsend_2_pdf` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.## Running an actionDocsend2pdf needs no account connection. Assume the oo CLI is installed and signed in. **Do not run `oo auth login` proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails.**1. Inspect the contract** to get the authoritative input/output schema before building a payload:```bashoo connector schema "docsend_2_pdf" --action "<action_name>"```**2. Run the action** with a JSON payload that matches the input schema:```bashoo connector run "docsend_2_pdf" --action "<action_name>" --data '<json>' --json```- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.- The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`.Each action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.## Available actions- `convert` — Convert a DocSend document URL to PDF and return JSON-safe download metadata.## Safety- Untagged actions are reads (get / list / search) — safe to run directly.- **Actions tagged `[write]` change Docsend2pdf state — confirm the exact payload and effect with the user before running.**- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**## First-time setupThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>): ```bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux ``` ```powershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell ```- **Not signed in / authentication error** — sign in to your OOMOL account once: ```bash oo auth login ```- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.## Resources- Docsend2pdf homepage: https://docsend2pdf.com

Frequently asked questions

Oo Docsend 2 PDF