Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Generate, inspect, validate, and fix PDF, Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) documents: turn structured content into render-ready artifacts, verify structural and output quality…
Install Documents
$ npx skills add magnus919/agent-skills --skill documents -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/agent-skills documents --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/documents .claude/skills/documents && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "documents" agent skill from https://github.com/magnus919/agent-skills/tree/main/documents into .claude/skills/documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documents", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/magnus919/agent-skills/tree/main/documentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add magnus919/agent-skills --skill documents -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/agent-skills documents --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/documents .agents/skills/documents && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "documents" agent skill from https://github.com/magnus919/agent-skills/tree/main/documents into .agents/skills/documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documents", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill documents -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/agent-skills documents --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/documents .cursor/skills/documents && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "documents" agent skill from https://github.com/magnus919/agent-skills/tree/main/documents into .cursor/skills/documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documents", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/magnus919/agent-skills.git --path documents--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add magnus919/agent-skills --skill documents -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/agent-skills documents --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/documents .gemini/skills/documents && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "documents" agent skill from https://github.com/magnus919/agent-skills/tree/main/documents into .gemini/skills/documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documents", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install magnus919/agent-skills documentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add magnus919/agent-skills --skill documents -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/documents .github/skills/documents && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "documents" agent skill from https://github.com/magnus919/agent-skills/tree/main/documents into .github/skills/documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documents", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill documents -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install magnus919/agent-skills documents --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/documents .opencode/skills/documents && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "documents" agent skill from https://github.com/magnus919/agent-skills/tree/main/documents into .opencode/skills/documents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documents", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
documents- GitHub stars
- 116
- Token cost
- ~2.3k tokens
- SKILL.md length
- 910 words
- Files
- 19 (incl. scripts, references)
- Skills in repo
- 130
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate, inspect, validate, and fix PDF, Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) documents: turn structured content into render-ready artifacts, verify structural and output quality…
- Works in 6 steps: Scope → Content model → Template → …
- A task involves creating
- SKILL.md covers When to use, When not to use, The Shared Workflow and Exit conditions, plus 2 more sections
- Runs Python scripts from its folder; calls python3
What it does
Documents is an agent skill from magnus919/agent-skills. Generate, inspect, validate, and fix PDF, Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) documents: turn structured content into render-ready artifacts, verify structural and output quality before delivery, and repair broken files. Use when a task involves creating, editing, converting, or validating office documents and PDFs. Do not use for ebook packaging (use epub), for images, video, or other media production, for API or code documentation, or for data pipelines (use data-engineering).
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 23 other files, including scripts and reference files (for example `README.md`, `evals/evals.json` and `references/excel.md`). Compatibility notes: Python 3.8+ for scripts; validation uses only the standard library. Optional renderers for the render check: poppler-utils (pdftoppm) for PDF and LibreOffice…
It sits in Documents & Office, covering Excel spreadsheets, PowerPoint presentations and Data pipelines and ETL. It works with Microsoft Excel, Microsoft PowerPoint and Microsoft Word. The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.
When your agent uses it
- A task involves creating
- Validating office documents and PDFs
- Ebook packaging (use epub)
- Other media production
Example prompts
- “/documents”
Requirements
- Python 3
- Compatibility (from SKILL.md): Python 3.8+ for scripts; validation uses only the standard library. Optional renderers for the render check: poppler-utils (pdftoppm) for PDF and LibreOffice for Office formats; both degrade gracefully when absent. Portable across all AgentSkills-compatible harnesses.
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit c545c2b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Python 3.8+ for scripts; validation uses only the standard library. Optional renderers for the render check: poppler-utils (pdftoppm) for PDF and LibreOffice for Office formats; both degrade gracefully when absent. Portable across all AgentSkills-compatible harnesses.
From compatibility in the SKILL.md frontmatter.
Context cost
Documents loads about 2.3k tokens when it runs, and up to ~7.5k if it reads all its reference files. Until then it costs about 127 tokens; SKILL.md has 910 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from magnus919/agent-skills at commit c545c2b, republished under its MIT licence (© magnus919). 910 words, ~2,265 tokens.
Download SKILL.mdSave it as
.claude/skills/documents/SKILL.md (or your agent's skills folder). This skill also uses 18 other files; get the full folder from GitHub.- name
- documents
- description
- Generate, inspect, validate, and fix PDF, Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) documents: turn structured content into render-ready artifacts, verify structural and output quality before delivery, and repair broken files. Use when a task involves creating, editing, converting, or validating office documents and PDFs. Do not use for ebook packaging (use epub), for images, video, or other media production, for API or code documentation, or for data pipelines (use data-engineering).
- compatibility
- Python 3.8+ for scripts; validation uses only the standard library. Optional renderers for the render check: poppler-utils (pdftoppm) for PDF and LibreOffice for Office formats; both degrade gracefully when absent. Portable across all AgentSkills-compatible harnesses.
- license
- MIT
- metadata.skills
- documents, pdf, docx, xlsx, pptx, word, excel, powerpoint, office, report, generation
- metadata.tags
- documents, pdf, docx, xlsx, pptx, word, excel, powerpoint, office, generation, validation
Documents — PDF, Word, Excel & PowerPoint Skill
One skill for the four most common document formats. All four share a single
agent workflow — structured content in, render-ready, validated artifact out —
so they live in ONE family skill with per-format references, following the
epub precedent. Load the shared workflow below, then pull the per-format
reference for the format you are actually touching.
| Format | Extension | Reference (load on demand) |
|---|---|---|
.pdf | references/pdf.md | |
| Word | .docx | references/word.md |
| Excel | .xlsx | references/excel.md |
| PowerPoint | .pptx | references/powerpoint.md |
| All formats | — | references/output-quality.md |
Generation templates for each format live in templates/, and the validation script with per-format fixtures lives in scripts/.
When to use
Load this skill when the task involves any of the four formats:
- Generate: build a report, memo, spreadsheet, or deck from structured content (markdown, JSON, data tables, outlines).
- Edit: modify an existing document's content, layout, or metadata in place.
- Extract: pull text, tables, or structure out of an existing file.
- Convert: move content between formats or from a data source into a document.
- Validate: check that a produced artifact is structurally sound and will render correctly before it is delivered.
When not to use
- Ebooks and EPUB — use the
epubskill; it owns the EPUB container, reading order, and package validation. - Images, video, and other media — this skill covers document formats only; route media production to the appropriate media skills.
- Code and API documentation sites — use the technical-documentation and documentation-site conventions, not office documents.
- Data pipelines — moving or transforming raw data belongs to
data-engineering; Excel here is a deliverable format, not a data store. - Office documents to Markdown — converting an existing office document
(docx, xlsx, pptx, pdf, odt, rtf, epub, csv) to GitHub-Flavored Markdown
belongs to the
anydocskill; this skill owns generation, editing, and validation, not document-to-markdown extraction.
The Shared Workflow
Every document task follows the same six steps, regardless of format. Deep format-specific detail is deferred to the per-format reference — read it at the step where it matters.
1. Scope
Pin down what the document is for before touching a file:
- Audience and purpose — who reads it and what decision it supports.
- Format — PDF (fixed layout, print, archival), Word (editable prose, review), Excel (data, calculations), PowerPoint (presentation).
- Boundaries — page/slide count, size limits, brand or style constraints.
- Source of truth — the structured content the document is generated from (markdown, JSON, CSV, outline), so the artifact is reproducible.
2. Content model
Represent the document's content as structured data before rendering:
- A title, sections/headings, body text, and metadata for prose documents.
- A table model (headers, rows, column types) for spreadsheets.
- A slide outline (title + bullets per slide, speaker notes) for decks.
- Keep content and layout separate: content in the model, layout in the template. This is what makes regeneration cheap.
3. Template
Choose the generation template for the target format from templates/:
- templates/pdf-template.md — fixed-layout document skeleton (print-ready HTML/CSS or LaTeX source).
- templates/word-template.md — Word processing document structure (styles, headings, tables).
- templates/excel-template.md — workbook structure (sheets, cells, shared strings, formulas).
- templates/powerpoint-template.md — slide deck structure (slides, layouts, notes).
Fill the [fill: ...] markers in the template with content from the content
model. Templates are the contract between content and layout — changing the
template is how you change appearance without touching content.
Show full SKILL.md (383 more words)Show less
4. Render
Produce the artifact file:
- PDF — render the template to PDF (print CSS in a browser or engine, or a LaTeX toolchain). See references/pdf.md for tooling.
- Word / Excel / PowerPoint — write the OOXML package directly (stdlib
zipfile+ XML for small artifacts) or with the conventional library for the format (python-docx, openpyxl, python-pptx). See the per-format reference for the exact package layout to produce.
5. Validate
Never deliver unvalidated output. Run the validation script:
python3 scripts/validate-documents.py --render-check --json report.pdf brief.docx data.xlsx deck.pptxThe script performs structural sanity (container signatures, required
parts, XML well-formedness) and, when a renderer is installed, a render
check (actually renders the file). When no renderer is present it reports
unavailable instead of failing — validation never hard-requires a renderer.
See references/output-quality.md for the full
output-quality checklist, and the fixture files in
fixtures/ (one per format) to smoke-test the script itself:
python3 scripts/validate-documents.py --json fixtures/sample.pdf fixtures/sample.docx fixtures/sample.xlsx fixtures/sample.pptx6. Deliver
Hand off the artifact with its provenance:
- The source content model (so it can be regenerated).
- The template version used.
- The validation result (structure passed; render checked or unavailable).
- Any known deviations (fonts substituted, images downscaled, layout drift).
Exit conditions
The task is complete when the artifact exists, passes structural validation (and the render check when a renderer is available), and the content matches the agreed scope. Stop after delivering the validated artifact with its provenance; do not keep iterating on layout without a new scope instruction.
Scripts
All scripts live in scripts/ relative to this skill's directory and
follow cli-builder conventions: --json for machine output, non-interactive,
errors to stderr. Run with --help for full flag details.
validate-documents.py — Structural Sanity + Render Check
python3 scripts/validate-documents.py report.pdf # human report
python3 scripts/validate-documents.py --json report.pdf # machine report
python3 scripts/validate-documents.py --render-check --json report.pdf data.xlsx deck.pptxBehavior:
- Structural sanity per format: PDF header/EOF/page objects; OOXML ZIP
container,
[Content_Types].xml, required parts, XML well-formedness. Legacy.doc/.xls/.pptfiles are recognized via OLE2 magic bytes. - Render check (
--render-check): renders PDF viapdftoppm/mutool/gsand Office formats via LibreOffice. Reportsunavailable— exit 0 — when no renderer is installed (graceful degradation, never a crash). - Exit codes: 0 all pass (or render check unavailable); 1 a file fails structure or rendering; 2 usage/I/O error.
- JSON output: top-level
status(ok/fail/unavailable/error) with per-file checks and render results.
Related skills
- epub — ebook container skill; the sibling family-skill precedent for this format family.
- data-engineering — data pipelines and transformation; Excel is a deliverable format here, not a data store.
- cli-builder — the CLI conventions the validation
script follows (
--json, non-interactive, exit codes).
© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 18 other files (scripts, references) in documents of magnus919/agent-skills.
- SKILL.md
- README.md
- evals/evals.json
- fixtures/sample.docx
- fixtures/sample.pdf
- fixtures/sample.pptx
- fixtures/sample.xlsx
- references/excel.md
- references/output-quality.md
- references/pdf.md
- references/powerpoint.md
- references/word.md
- scripts/validate-documents.py
- templates/excel-template.md
- templates/pdf-template.md
- templates/powerpoint-template.md
- … and 3 more
Open the folder on GitHubat commit c545c2b
Compare with similar skills
Documents next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Documents this skillmagnus919/agent-skills | 116 | — | ~2.3k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 782 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Markitdownjimmc414/Kosmos | 595 | 2 repos | ~1.7k | Automated safety check: Pass | None | |
| Office DocumentsZS520L/HanakoPro | 103 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| PaperJSX Document Generatorcomposio-community/awesome-codex-skills | 17k | — | ~842 | Automated safety check: Pass | Apache-2.0 | |
| Skill Doc Deliverynyldn/claude-octopus | 4.2k | 1 repos | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
Markitdown
jimmc414/Kosmos
Convert various file formats (PDF, Office documents, images, audio, web content, structured data) to Markdown optimized for LLM processing.
Office Documents
ZS520L/HanakoPro
A skill your agent uses when the user asks to open, read, inspect, understand, summarize, analyze, extract tables/text from, modify, update, repair, split, merge, rotate, or convert information from…
PaperJSX Document Generator
composio-community/awesome-codex-skills
Generates PPTX, DOCX, XLSX and PDF files from a JSON layout spec through PaperJSX's packages, creating new documents rather than editing them.
Skill Doc Delivery
nyldn/claude-octopus
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables
Exam Ingest
ZeKaiNie/universal-examprep-skill
从学生上传的课件/大纲/老师勾的重点/真题，一键初始化并验证备考工作区：解析 PDF、DOCX、PPTX、 XLSX、常见独立图片与 txt/md，建立分章节 LLM Wiki、标准题库、结构化接管队列与进度状态；仅在 Python 确实无法运行时 明确降级为手动写盘。当工作区尚未建立、资料发生变化、或建库 readiness 被阻断时使用。
More from magnus919/agent-skills
All 130 skills in this repoArtifact Pyramids
magnus919/agent-skills
Organize durable agent research outputs as summaries, analysis, and evidence dossiers.
Ascii City Engine
magnus919/agent-skills
Build portable, first-person colored ASCII city engines and small GIS-derived city packs.
Color Management
magnus919/agent-skills
Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.
Data Scientist
magnus919/agent-skills
A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…
Docker Compose
magnus919/agent-skills
Use Docker Compose to define, run, debug, and harden multi-container applications.
Fpga Development
magnus919/agent-skills
Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.
Related
Categories
Questions about Documents
What does Documents do?
Generate, inspect, validate, and fix PDF, Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) documents: turn structured content into render-ready artifacts, verify structural and output quality…. Documents is an agent skill from magnus919/agent-skills.pptx) documents: turn structured content into render-ready artifacts, verify structural and output quality before delivery, and repair broken files.
When should I use Documents?
Documents fits situations like: A task involves creating; validating office documents and PDFs; ebook packaging (use epub); other media production.
How do I install Documents in Claude Code?
Run `npx skills add magnus919/agent-skills --skill documents -a claude-code`. Or copy the skill folder (documents in magnus919/agent-skills) into .claude/skills/documents in your project. Claude Code loads it when a task matches its description.
How do I install Documents in Codex?
Run `npx skills add magnus919/agent-skills --skill documents -a codex`. Or copy the skill folder (documents in magnus919/agent-skills) into .agents/skills/documents in your project. Codex loads it when a task matches its description.
Can I use Documents in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/agent-skills --skill documents -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documents, .gemini/skills/documents, .github/skills/documents and .opencode/skills/documents in your project.
What does Documents need to run?
Going by SKILL.md and its folder, Documents needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3. Compatibility (from SKILL.md): Python 3.8+ for scripts; validation uses only the standard library. Optional renderers for the render check: poppler-utils (pdftoppm) for PDF and LibreOffice for Office formats; both degrade gracefully when absent. Portable across all AgentSkills-compatible harnesses..
Does Documents access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Documents safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Documents use?
Documents is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Documents use?
About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.3k tokens, read only when the agent opens those files.
What are the alternatives to Documents?
Skills that share tags, products or a category with Documents: Markitdown (ImCa0/just-laws, 782 stars), Markitdown (jimmc414/Kosmos, 595 stars), Office Documents (ZS520L/HanakoPro, 103 stars) and PaperJSX Document Generator (composio-community/awesome-codex-skills, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Documents?
magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 116 GitHub stars. The repository holds 130 skills in this directory. The repository was last updated on October 8, 2026.
Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.