skilldrop-cli 0.16.3__py3-none-any.whl

skilldrop_cli/data/packs/api-builder/skills/tool-use-schema-writer/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: tool-use-schema-writer
+description: Takes a function description (name, purpose, parameters) and writes a valid Anthropic tool_use JSON schema, with type annotations, required fields, and a description for each parameter. Produces a Python usage snippet for client.messages.create(tools=[...]). Use when wiring a Claude agent to a function or API, designing tools for a multi-agent system, or documenting an existing tool for agent consumption.
+---
+
+# tool-use-schema-writer
+
+Converts a natural-language function description into a valid Anthropic `tool_use` definition. The output is ready to paste into `client.messages.create(tools=[...])`. This skill enforces the two constraints that cause most tool-use bugs: descriptions that are too vague for the model to choose the right tool, and missing `required` arrays that cause the model to omit non-optional fields.
+
+## How to respond
+
+### Step 1 — Intake
+
+Ask the user to describe the function. Collect:
+- **Name** (snake_case preferred; the model uses this to call the tool)
+- **Purpose** (one sentence: what does this function do and when should the model call it?)
+- **Parameters**: for each — name, type, what it means, whether it's required
+- **Return value** (optional — for documentation purposes only; the model doesn't see it)
+
+If they share existing code (Python, TypeScript, etc.), read the function signature and docstring directly.
+
+### Step 2 — Write the tool definition
+
+Produce a valid Anthropic tool definition:
+
+```json
+{
+  "name": "function_name",
+  "description": "One to three sentences. State what the function does, when the model should call it (the decision condition), and what it returns. Avoid vague descriptions like 'performs an operation' — the model reads this to decide whether to call the tool.",
+  "input_schema": {
+    "type": "object",
+    "properties": {
+      "param_name": {
+        "type": "string",
+        "description": "What this parameter controls and what values are valid. Include the unit if numeric (e.g., 'timeout in seconds, 1–300')."
+      },
+      "another_param": {
+        "type": "integer",
+        "description": "..."
+      },
+      "enum_param": {
+        "type": "string",
+        "enum": ["value_a", "value_b"],
+        "description": "Which mode to use. value_a does X; value_b does Y."
+      }
+    },
+    "required": ["param_name"]
+  }
+}
+```
+
+Valid JSON Schema types for Anthropic tool parameters: `"string"`, `"integer"`, `"number"`, `"boolean"`, `"array"`, `"object"`, `"null"`. Arrays need `"items"`. Objects need `"properties"` and their own `"required"`.
+
+### Step 3 — Validate
+
+Check the definition against these rules before outputting:
+- Every parameter in `"required"` exists in `"properties"`
+- No parameter has an empty `"description"` — the model needs these to fill values correctly
+- The top-level `"description"` names a decision condition ("call this when X"), not just what it does
+- Enum values are listed in the parameter description with a one-phrase explanation each
+- Nested objects have their own `"required"` arrays
+
+### Step 4 — Python usage snippet
+
+Produce the Python snippet:
+
+```python
+import anthropic
+
+client = anthropic.Anthropic()
+
+tools = [
+    {
+        "name": "function_name",
+        "description": "...",
+        "input_schema": { ... }
+    }
+]
+
+response = client.messages.create(
+    model="claude-sonnet-5-5",
+    max_tokens=1024,
+    tools=tools,
+    messages=[{"role": "user", "content": "Your prompt here"}]
+)
+
+# Handle tool use
+if response.stop_reason == "tool_use":
+    tool_use_block = next(b for b in response.content if b.type == "tool_use")
+    tool_input = tool_use_block.input  # dict matching your schema
+    result = function_name(**tool_input)
+    # Send result back in a follow-up message
+```
+
+### Step 5 — Multi-tool note
+
+If the user describes multiple functions, produce one JSON array with all tools and remind them: the model chooses among all tools on each turn, so descriptions must be distinct enough to make the right call unambiguous. If two tools do similar things, the description must name the exact condition that separates them.
+
+## Anti-patterns
+
+- **Descriptions that restate the function name.** `"Gets the weather"` for a function named `get_weather` tells the model nothing about when to call it. Descriptions must name the decision condition.
+- **Omitting the `required` array.** Without `required`, all fields are optional — the model will skip non-optional parameters, causing runtime errors.
+- **Enum values without descriptions.** `"enum": ["asc", "desc"]` without explanation leaves the model guessing; it will sometimes pick the wrong value.
+
+For the agent loop that calls these tools, see `agent-loop-design`. For orchestrating multiple agents that each expose tool schemas, see `subagent-design`.
+
+## Quality bar
+
+- **Descriptions are decision conditions, not function names restated.** `"Gets the weather"` is not a description — `"Returns the current temperature and conditions for a given city. Call this when the user asks about current weather, not forecasts."` is.
+- **Required arrays are never omitted.** An omitted `required` array means all fields are optional — the model will skip fields the function actually needs and the call will fail at runtime.
+- **Enum values always have descriptions.** `"enum": ["asc", "desc"]` without a description leaves the model guessing which to use.

skilldrop_cli/data/packs/api-builder/skills/tool-use-schema-writer/evals/eval_queries.json

@@ -0,0 +1,30 @@
+[
+  {
+    "query": "Write the tool_use JSON schema for this function so Claude can call it",
+    "should_trigger": true
+  },
+  {
+    "query": "Turn this TypeScript API client method into an Anthropic tool definition",
+    "should_trigger": true
+  },
+  {
+    "query": "I have three functions for my agent — write their tool schemas so the model picks the right one",
+    "should_trigger": true
+  },
+  {
+    "query": "Document this existing endpoint as a tool the agent can consume, with required fields",
+    "should_trigger": true
+  },
+  {
+    "query": "Design the control loop for my tool-using agent — stop conditions and retries",
+    "should_trigger": false
+  },
+  {
+    "query": "Split this workflow across an orchestrator and specialist subagents",
+    "should_trigger": false
+  },
+  {
+    "query": "Draft the OpenAPI contract for our new public REST API",
+    "should_trigger": false
+  }
+]

skilldrop_cli/data/packs/api-builder/skills/tool-use-schema-writer/evals/evals.json

@@ -0,0 +1,18 @@
+{
+  "skill_name": "tool-use-schema-writer",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Write the Claude tool definition for this Python function in our Acme order service:\n\ndef search_orders(customer_id: str, status: str | None = None, placed_after: str | None = None, sort: str = 'desc', limit: int = 20):\n    \"\"\"Find a customer's orders. status is one of pending, shipped, delivered, cancelled. placed_after is an ISO date. sort is by order date, asc or desc. limit 1-100.\"\"\"\n\nThe agent also has a separate get_order(order_id) tool, so the descriptions need to keep them apart.",
+      "assertions": [
+        "Produces a valid Anthropic tool definition with name, description, and input_schema of type object",
+        "The top-level description names a decision condition (when to call search_orders versus get_order), not just a restatement of the function name",
+        "A required array is present and contains customer_id; every name in required exists in properties",
+        "Every parameter has a non-empty description, and limit states its valid range (1-100)",
+        "The status and sort enums list their values with a one-phrase explanation of each value",
+        "Includes a Python snippet passing the tool to client.messages.create(tools=[...]) and handling stop_reason == 'tool_use'",
+        "Does not invent parameters, enum values, or behaviors not in the supplied signature and docstring"
+      ]
+    }
+  ]
+}

skilldrop_cli/data/packs/api-builder/skills/tool-use-schema-writer/manifest.json

@@ -0,0 +1,11 @@
+{
+  "name": "tool-use-schema-writer",
+  "version": "1.0.0",
+  "description": "Takes a function description (name, purpose, parameters) and writes a valid Anthropic tool_use JSON schema, with type annotations, required fields, and a description for each parameter. Produces a Python usage snippet for client.messages.create(tools=[...]). Use when wiring a Claude agent to a function or API, designing tools for a multi-agent system, or documenting an existing tool for agent consumption.",
+  "entrypoint": "SKILL.md",
+  "deps": { "npm": [], "pip": [] },
+  "env": { "required": [], "optional": [] },
+  "related": ["agent-loop-design", "subagent-design"],
+  "tags": ["claude-api", "tool-use", "json-schema", "sdk", "agents"],
+  "model": { "tier": "standard", "rationale": "Schema generation from a natural-language description — structured output task that fits standard tier." }
+}

skilldrop_cli/data/packs/converters/pack.json

@@ -0,0 +1,66 @@
+{
+  "description": "Turn Markdown into Word, Excel and HTML files that people outside engineering can open, turn their files back into Markdown, and render diagrams to images. Standard-library Python scripts, with nothing to install.",
+  "display_name": "Converters",
+  "keywords": ["convert", "markdown", "word", "docx", "excel", "xlsx", "html", "mermaid"],
+  "links": {
+    "documentation": "https://sananthanarayan.github.io/skilldrop/packs/converters/"
+  },
+  "maintainers": [
+    {
+      "name": "sananthanarayan"
+    }
+  ],
+  "first-value": {
+    "audience-posture": "technical",
+    "prerequisites": ["Python 3.9 or later", "A Markdown file with a heading or two, and a table if you want a spreadsheet"],
+    "starter-task": "Send a Markdown report as a Word document and its tables as a spreadsheet",
+    "starter-prompt": "Convert reports/q3-review.md to a Word document for the Acme account team, and put its tables in an Excel workbook for finance.",
+    "verification": "md-to-docx writes q3-review.docx with the headings in Word's navigation pane and a WARN line for anything it dropped, and md-to-xlsx writes q3-review.xlsx with one sheet per table, numbers typed as numbers, and a frozen, filtered header row.",
+    "recovery": "If the script says python3 is not found, install Python 3.9 or later. If a skill does not activate, ask for it by name (\"use md-to-docx\"). If a table lands as text, read the per-sheet counts md-to-xlsx printed: a unit typed inside the number cells is the usual cause."
+  },
+  "requires": ["core"],
+  "journey": {
+    "when": "Your draft is in Markdown, but the people who need it work in Word, Excel or a browser, or they sent you their files and you want to work on them as Markdown.",
+    "you_bring": [
+      "the Markdown draft, or the Word, PDF, Excel or HTML files you were sent",
+      "any Mermaid diagrams the draft contains",
+      "a brand.json from brand-kit, if the Word file should be in your brand",
+      "who it is for, and whether they edit it, calculate with it or only read it"
+    ],
+    "time": "10 to 20 minutes",
+    "steps": [
+      {
+        "skill": "file-to-markdown",
+        "you_do": "If you start from someone else's files, hand them over.",
+        "you_get": "Markdown you can edit and diff, with a count of what could not come across (images, charts, comments, formulas, tracked changes)."
+      },
+      {
+        "skill": "output-hygiene",
+        "you_do": "Run it on the finished draft before it leaves the team.",
+        "you_get": "The draft with invisible characters and generated-by trailers stripped, and machine-sounding lines flagged with rewrites."
+      },
+      {
+        "skill": "mermaid-render",
+        "you_do": "If the draft has Mermaid diagrams, render them.",
+        "you_get": "Each diagram checked for the errors that stop it rendering, then an SVG or PNG per diagram to embed in the Word or HTML version (PNG and SVG need mermaid-cli installed)."
+      },
+      {
+        "skill": "md-to-docx",
+        "you_do": "Convert the draft for readers who will edit or comment in Word.",
+        "you_get": "A .docx with real headings, live links, tables and embedded images, plus a list of anything dropped.",
+        "decide": "Send it, or fix the warnings in the Markdown and convert again."
+      },
+      {
+        "skill": "md-to-xlsx",
+        "you_do": "Convert the tables for readers who will filter or total them.",
+        "you_get": "A .xlsx with one sheet per table, typed numbers, dates and percentages, and formulas off unless you ask."
+      },
+      {
+        "skill": "md-to-html",
+        "you_do": "Convert the draft for readers who only need to read it in a browser.",
+        "you_get": "One self-contained, print-friendly HTML file with images embedded, so it still works when emailed."
+      }
+    ],
+    "you_end_with": "The same content in the format each reader uses, with nothing dropped silently, and a Markdown source you can keep editing."
+  }
+}

skilldrop_cli/data/packs/converters/skills/file-to-markdown/SKILL.md

@@ -0,0 +1,103 @@
+---
+name: file-to-markdown
+description: Convert a Word document, PowerPoint deck, Excel workbook, web page, CSV, JSON, text file or PDF into clean Markdown that keeps headings, lists, tables, links, bold and italic, slide titles and speaker notes, and reports everything it dropped (images, charts, comments, formulas, tracked changes), so the content can be read, reviewed or fed to another skill. Use when the user hands over a .docx, .pptx, .xlsx, .html, .csv, .json or .pdf and says "read this", "turn this into markdown", "extract the text", or wants it critiqued or briefed.
+---
+
+# file-to-markdown
+
+You turn the files people actually send (a Word draft, last quarter's deck, a budget workbook,
+a saved web page) into Markdown an agent can read reliably. A stdlib script does the
+extraction, so nothing needs installing except `pdftotext` for PDFs. The Markdown is rarely
+the end product: it is the input to `doc-critique` (review it), `brief-intake` (structure it),
+or a rewrite that goes back out through `md-to-docx` or `md-to-html`.
+
+## How to respond
+
+1. **Ask once for anything missing.** Usually only the file is needed:
+
+   > Send me the file (or its path). Anything else is optional:
+   > 1. **What you want next:** just the Markdown, a critique, or a brief. *Default: just the Markdown.*
+   > 2. **For big workbooks:** a row limit per sheet. *Default: every row.*
+
+2. **Run the script.**
+
+   ```bash
+   # Claude Code
+   python3 "${CLAUDE_SKILL_DIR}/scripts/to_markdown.py" input.docx -o input.md
+   # Other IDEs (from the skill folder)
+   python3 scripts/to_markdown.py input.docx -o input.md
+   ```
+
+   `-o -` writes to stdout. `--max-rows 200` caps each sheet of an `.xlsx`.
+
+   | Input | What comes through |
+   |---|---|
+   | `.docx` | Headings by style (Title, Heading 1–6, outline level), bulleted and numbered lists with nesting, tables, bold, italic, hyperlinks |
+   | `.pptx` | One `## Slide N: title` section per slide, bullets with levels, tables, speaker notes as a quote |
+   | `.xlsx` | One table per sheet, shared strings, numbers as stored, dates as `YYYY-MM-DD`, cached formula values |
+   | `.html` | Headings, lists, tables, links, code blocks, quotes; scripts, styles and nav menus dropped |
+   | `.csv` / `.tsv` | One table, delimiter detected |
+   | `.json` | An array of objects becomes a table; an object becomes a key/value table plus a table per array |
+   | `.txt` / `.md` | Passed through |
+   | `.pdf` | Through `pdftotext`. Tables from aligned columns, lists from indentation, short standalone lines as `###` headings (guessed, and said so); pages with side-by-side columns are read in column order with nothing inferred. No images |
+
+3. **PDF without `pdftotext`.** The script stops with install steps (`brew install poppler`
+   on macOS, `sudo apt install poppler-utils` on Debian/Ubuntu). Pass those on; don't try to
+   read the PDF bytes yourself. A PDF with no text layer is a scan and needs OCR, which this
+   skill does not do.
+
+4. **Old binary formats** (`.doc`, `.ppt`, `.xls`, `.rtf`, `.pages`, `.key`): the script
+   refuses and names the format to save as. On macOS, `textutil -convert docx file.doc`
+   handles `.doc` and `.rtf`, though it writes no heading styles, so check the levels.
+
+5. **Report what was dropped, every time.** The script prints three kinds of line to stderr:
+   `converted …` (what was kept), `dropped …` (images, charts, comments, footnotes, formulas,
+   tracked changes, headers and footers), and `note: …` (headings inferred from font size,
+   merged cells, truncated sheets). Put them at the top of the reply in plain words: "The
+   deck has 4 charts that are not in the Markdown; their numbers are missing from what I read."
+
+6. **Then do the next step the user asked for.** When a critique or brief depends on a chart
+   or comment that was dropped, say so in that output too. Don't let it read as complete.
+
+**Non-interactive runs** (subagent, CI, headless): convert with the defaults and prefix the
+reply with the dropped list. If no file is given, or the PDF needs `pdftotext` and it is
+missing, emit `BLOCKED: need <the file | pdftotext on PATH>` and stop.
+
+## Useful references in this skill
+
+- [`scripts/to_markdown.py`](scripts/to_markdown.py): the converter (stdlib only; `pdftotext` optional for PDF)
+- [`examples/mixed-inputs.md`](examples/mixed-inputs.md): a Word brief, a deck, a workbook and a web page converted, with the real Markdown and stderr report
+
+## Quality bar
+
+- **Structure survives.** A heading in the source is a heading in the Markdown, a list is a list, a table is a table. Not a wall of paragraphs.
+- **Losses are stated, with counts.** "2 charts, 1 comment and 14 formulas are not in this", never silence.
+- **Nothing is added.** The Markdown holds only what the file holds: no summaries, no invented headings, no filled-in empty cells.
+- **Speaker notes stay attached to their slide,** because that is often where the real argument is.
+- **Numbers are copied as stored.** No rounding, no currency symbols added; dates converted only when the cell is formatted as a date.
+- **Inferred structure is flagged.** When headings come from font size instead of styles, the reply says to check the levels.
+
+## When to use this skill
+
+- ✅ Someone sends a .docx, .pptx or .xlsx and the user wants it reviewed, summarised or rewritten
+- ✅ Feeding a document into `doc-critique` or `brief-intake`
+- ✅ Pulling the text and tables out of a saved web page or a PDF report
+- ✅ Turning a CSV or JSON export into a readable table
+
+## When NOT to use this skill
+
+- ❌ Going the other way, Markdown to Word; use `md-to-docx`
+- ❌ Markdown to a web page; use `md-to-html`
+- ❌ Markdown tables into a workbook; use `md-to-xlsx`
+- ❌ Messy notes, a Slack thread or a transcript that are already text; use `brief-intake` directly
+- ❌ A document that is already Markdown and needs reviewing; use `doc-critique` directly
+
+## Anti-patterns to avoid
+
+- ❌ **Summarising instead of converting.** The user asked for the document; give them the document, then summarise if asked.
+- ❌ **Hiding the dropped list** below the Markdown, or leaving it out because "it's only images". A chart is often the slide's whole point.
+- ❌ **Reading a PDF as raw bytes** when `pdftotext` is missing. Ask the user to install it or export the PDF to .docx.
+- ❌ **Treating inferred headings as fact.** A bold, large line in an unstyled document might be a pull quote.
+- ❌ **Critiquing a deck from its Markdown** without saying the charts and images were not seen.
+- ❌ **Showing the machinery.** The reply and the artifact are for the person who asked. Don't mention this skill, its files, templates, caps or internal terms, or that the run is non-interactive. Name another skill once, at the end, as a suggested next step, never inside the artifact.
+- ❌ **A bare `BLOCKED` line.** Keep the `BLOCKED: need <X>` line, then write for a person: what is missing in plain words, what you will produce once you have it, and anything the request already lets you say.

skilldrop_cli/data/packs/converters/skills/file-to-markdown/evals/eval_queries.json

@@ -0,0 +1,34 @@
+[
+  {
+    "query": "Convert this Word doc to markdown",
+    "should_trigger": true
+  },
+  {
+    "query": "Extract the text and tables from budget.xlsx so you can read it",
+    "should_trigger": true
+  },
+  {
+    "query": "Here's the deck as a pptx, pull out the slide text and speaker notes",
+    "should_trigger": true
+  },
+  {
+    "query": "Turn this saved HTML page into clean markdown",
+    "should_trigger": true
+  },
+  {
+    "query": "Convert my markdown notes into a .docx for the client",
+    "should_trigger": false
+  },
+  {
+    "query": "Make an HTML version of README.md I can email",
+    "should_trigger": false
+  },
+  {
+    "query": "Here's a messy Slack thread, turn it into a brief for the design doc",
+    "should_trigger": false
+  },
+  {
+    "query": "Review this design doc markdown and tell me what to fix",
+    "should_trigger": false
+  }
+]

skilldrop_cli/data/packs/converters/skills/file-to-markdown/evals/evals.json

@@ -0,0 +1,27 @@
+{
+  "skill_name": "file-to-markdown",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Northwind sent us their Q3 roadmap as northwind-q3.pptx (14 slides, a few charts, speaker notes on most slides). Turn it into markdown so we can critique it.",
+      "assertions": [
+        "Runs to_markdown.py on northwind-q3.pptx and writes a .md file",
+        "Each slide is a '## Slide N: title' section, in slide order",
+        "Speaker notes appear under their own slide, not collected at the end",
+        "States at the top of the reply how many charts and images were dropped, using the script's counts",
+        "Says that any critique cannot cover the chart contents because they were not converted",
+        "Does not invent slide content, numbers or chart values that are not in the converted text"
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Here's acme-contract-summary.pdf, can you get the text out?",
+      "assertions": [
+        "Runs to_markdown.py on the PDF",
+        "If pdftotext is missing, passes on the install step (brew install poppler / apt install poppler-utils) and does not attempt to read the PDF bytes",
+        "If it converts, says the PDF gives text only: no headings or tables recovered",
+        "Does not summarise or paraphrase in place of the converted text"
+      ]
+    }
+  ]
+}

skilldrop_cli/data/packs/converters/skills/file-to-markdown/evals/files/2/acme-contract-summary.pdf

@@ -0,0 +1,93 @@
+%PDF-1.3
+%���� ReportLab Generated PDF document (opensource)
+1 0 obj
+<<
+/F1 2 0 R /F2 3 0 R
+>>
+endobj
+2 0 obj
+<<
+/BaseFont /Helvetica /Encoding /WinAnsiEncoding /Name /F1 /Subtype /Type1 /Type /Font
+>>
+endobj
+3 0 obj
+<<
+/BaseFont /Helvetica-Bold /Encoding /WinAnsiEncoding /Name /F2 /Subtype /Type1 /Type /Font
+>>
+endobj
+4 0 obj
+<<
+/Contents 9 0 R /MediaBox [ 0 0 612 792 ] /Parent 8 0 R /Resources <<
+/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ]
+>> /Rotate 0 /Trans <<
+
+>> 
+  /Type /Page
+>>
+endobj
+5 0 obj
+<<
+/Contents 10 0 R /MediaBox [ 0 0 612 792 ] /Parent 8 0 R /Resources <<
+/Font 1 0 R /ProcSet [ /PDF /Text /ImageB /ImageC /ImageI ]
+>> /Rotate 0 /Trans <<
+
+>> 
+  /Type /Page
+>>
+endobj
+6 0 obj
+<<
+/PageMode /UseNone /Pages 8 0 R /Type /Catalog
+>>
+endobj
+7 0 obj
+<<
+/Author (anonymous) /CreationDate (D:20261001184656-04'00') /Creator (anonymous) /Keywords () /ModDate (D:20261001184656-04'00') /Producer (ReportLab PDF Library - \(opensource\)) 
+  /Subject (unspecified) /Title (untitled) /Trapped /False
+>>
+endobj
+8 0 obj
+<<
+/Count 2 /Kids [ 4 0 R 5 0 R ] /Type /Pages
+>>
+endobj
+9 0 obj
+<<
+/Filter [ /ASCII85Decode /FlateDecode ] /Length 357
+>>
+stream
+Gat=fcV=Qc&B=0eMXTIh9iD)E[G@;j)\8f#L)6N;=Vk#0!SXDhmjpBIM[(4#A24S.q.;lYn;q4"*Up"I1RF11\q@(2(%a#Jor.X#A6o,>M>Hbc,N<&"'[R>V&$7'=Kt(jD#+qZ)1Xai7'+\0kT?u1;-KgPGH2@iQT%*r7Is6,H3o3QSQ;W@!+;hl1,/i:*/R'l=f"%FN?W8m7#rG*&5ZMc.AtRGhi&G0XG3"r'TnKGlTJLP[cY:aT+fF?^+g>B]8Mc+o]3niHYlPL_R@):@,/,/bSNQ;a\q/Psi(UR2\e'WME%Gbif9?nqi$3hJpoljNQjKk<+^mq^:<5SL\>>lLB'.D:eqDEeY\To7~>endstream
+endobj
+10 0 obj
+<<
+/Filter [ /ASCII85Decode /FlateDecode ] /Length 326
+>>
+stream
+Gat=f]5E6T'Sc?E`P5Bc$kuW.$<n^^;muN+>W<!j?sC'*b1l[KTXILK7(s("o(S]5"`donh<b=b-(`ut6ikt.PZ\<<_OK>WGQC[<Gb#SaENp\\"n*FO_SZWS7CRr4()k(8j;6n+%u0Tu@:&rL<->TXY'\'!<?E!Q8+iiO*R>2[3ih`-aJ2`[R8/$$f#/`D5,[uE;VLK-ob!dIZR/M$&qca'5]8de([Tf`EJ'r5P<kA(Zr'\)dsuN[3.%Pc6`iY>UJp>p%qFYR@F[m%C>trC+O)PQ46`k[gaLdI-OMET*OGi[!9\(DFq3ia8@J$>L#"]=Y*RE~>endstream
+endobj
+xref
+0 11
+0000000000 65535 f 
+0000000061 00000 n 
+0000000102 00000 n 
+0000000209 00000 n 
+0000000321 00000 n 
+0000000514 00000 n 
+0000000708 00000 n 
+0000000776 00000 n 
+0000001037 00000 n 
+0000001102 00000 n 
+0000001549 00000 n 
+trailer
+<<
+/ID 
+[<7983528689757fefa7437d75e3d55037><7983528689757fefa7437d75e3d55037>]
+% ReportLab generated PDF document -- digest (opensource)
+
+/Info 7 0 R
+/Root 6 0 R
+/Size 11
+>>
+startxref
+1966
+%%EOF

skilldrop_cli/data/packs/converters/skills/file-to-markdown/examples/inputs/accounts.json

@@ -0,0 +1 @@
+[{"id":1,"name":"Acme","tags":["a","b"],"active":true},{"id":2,"name":"Northwind","region":"EU"}]

skilldrop_cli/data/packs/converters/skills/file-to-markdown/examples/inputs/fabrikam-status.html

@@ -0,0 +1,14 @@
+<!doctype html><html><head><meta charset="utf-8"><title>Fabrikam status</title><style>body{color:red}</style><script>track()</script></head>
+<body><nav><a href="/">Home</a></nav>
+<h1>Fabrikam service status</h1>
+<p>All systems <strong>operational</strong> except <em>search</em>. Details on the <a href="https://status.fabrikam.example/search">incident page</a>.</p>
+<h2>Open incidents</h2>
+<table><thead><tr><th>ID</th><th>Service</th><th>Since</th></tr></thead>
+<tbody><tr><td>INC-7</td><td>Search | EU</td><td>09:40 UTC</td></tr><tr><td>INC-8</td><td>Exports</td><td>11:05 UTC</td></tr></tbody></table>
+<h2>What to do</h2>
+<ol><li>Retry the search</li><li>If it fails, use filters:<ul><li>by date</li><li>by owner</li></ul></li></ol>
+<blockquote><p>We will post the next update by 14:00 UTC.</p></blockquote>
+<pre><code class="language-bash">curl -s https://status.fabrikam.example/api | jq .</code></pre>
+<p><img src="data:image/png;base64,AAAA" alt="graph"> <img src="uptime.png" alt="Uptime chart"></p>
+<script>more()</script>
+</body></html>