Open source agent skills: reusable instructions and supporting resources for focused tasks.
The skill catalog contains 27 focused, independently usable skills for research, documents, design, media, security, and development. They use local tools and supplied assets without requiring paid model-provider services. Narrated explainers and presenter edits have complete local routes; paid generation is optional and must be explicitly selected.
Browse the skill catalog, then read the selected skill's SKILL.md for its purpose, requirements, and workflow. Follow your agent's instructions for installing a local skill directory, including any bundled resources. Supported tools and environments are documented by each skill.
Copy the whole selected skill directory. Python requirements and optional Node lockfiles belong to that skill; install only the dependencies needed for the task in a writable project environment. The software and dependency reference lists each skill's required and optional tools, the tested versions, and install commands. Browser binaries, Office-compatible renderers, and media tools may need separate setup. Network access may be needed for initial downloads, but no OpenAI, Anthropic, Minimax, or other paid production API is a prerequisite.
skills/ Published skills and their catalog
<skill-name>/
SKILL.md Skill metadata and instructions
scripts/ Optional executable helpers
references/ Optional supporting documentation
assets/ Optional templates and other resources
tests/ Helper contracts, coverage inventory, and media integration tests
site/ Homepage HTML, styles, and browser interactions
tools/ Homepage builder and optional reference-corpus audit tools
DEPENDENCIES.md Required and optional software per skill
Dockerfile Sample Ubuntu 24.04 environment with every dependency
CONTRIBUTING.md Authoring, review, and verification guidance
AGENTS.md Instructions for agents working on this repository
CLAUDE.md Pointer to the shared agent instructions
.github/workflows/ Repository checks and GitHub Pages deployment
The skill layout follows the Agent Skills specification.
The homepage showcases every published skill in alphabetical order by name, with search, focus filters, local requirements, and all 51 theme-factory palettes. Visitors can choose from the dropdown, step through themes with Previous/Next arrows (wrapping at either end), or select a different random theme. The theme picker and all three buttons share a desktop row; narrower layouts place the picker above the buttons. Both the theme and focus dropdowns use consistently inset carets. Every choice is saved in the visitor's browser. Selecting a skill opens its rendered SKILL.md in an on-page reader with headings, lists, code blocks, tables, and expandable metadata. Clicking outside the reader, pressing Escape, or choosing Close returns to the catalog. A GitHub source link remains available, and supporting document links resolve relative to the skill directory at the corresponding source commit. Skill source links and setup guidance remain available without JavaScript.
Build and preview locally with Python 3.12 or later and the pinned homepage dependencies:
python3 -m venv .venv
. .venv/bin/activate
python3 -m pip install -r site/requirements.txt
python3 tools/build_site.py
python3 -m http.server 8000 --directory distOpen http://localhost:8000. The builder reads skills/README.md and the theme-factory guide, verifies catalog completeness and theme contrast contracts, and writes the homepage and its assets to ignored dist/. The build bundles rendered skill documents in inert HTML templates, so opening a reader requires no fetch or network access. Markdown is rendered with raw HTML disabled; frontmatter remains readable in a metadata disclosure. Edit the page layout in site/; update skill descriptions in the catalog and palettes in their original guide. --output <directory> selects another build destination. --source <directory> reads homepage/catalog/theme inputs from a snapshot, and --source-ref <commit> points skill links at that commit; Python helpers execute from the workflow commit checkout. Invalid catalog paths, incomplete catalog coverage, or invalid theme data fail the build with an error.
The GitHub Pages workflow follows the snapshot deployment pattern in pdf-unlocker. Every deployment includes current main at the root and every open same-repository PR targeting main at pr-preview/<number>/. The workflow runs on PR opened, reopened, synchronize, and closed events, pushes to main, and manual dispatch, matching the reference workflow. PR events have no base-branch filter; the packaged preview set includes only PRs targeting main. Closed or merged previews disappear at the next successful deployment. The shared pages concurrency group uses cancel-in-progress: false so a running deployment finishes before the next starts. Every run rebuilds the current snapshot set, including when GitHub replaces a pending run.
After deployment, a bot comment on each PR links to its preview and exact source commit. The existing comment updates on new commits; closed PR comments are marked removed. Fork PRs are excluded, matching the reference workflow. Relative assets support repository Pages URLs and custom domains.
In Settings > Pages > Build and deployment, select GitHub Actions as the source. The production URL is shown by the deployment's github-pages environment. The github-pages environment must allow deployments from main and PR merge refs (refs/pull/*/merge), and repository Actions settings must allow the workflow's pull-requests: write token to create comments. No repository settings are changed by the workflow. The workflow can preview its initial implementation before merge.
Preview jobs use pull_request and explicitly check out ${{ github.sha }}, matching pdf-unlocker. For open PRs this is the PR merge commit, as described in GitHub's event documentation. Only same-repository PRs can run these jobs; fork PRs are skipped. Build and comment helpers execute from that workflow commit, so same-repository contributors are trusted to modify deployment code. The snapshot helper reads only regular Git blobs for the homepage assets, skill catalog, published SKILL.md documents, and theme guide. It does not execute Python helpers from the individual snapshots. The workflow commit's renderer builds both production and every preview, so renderer changes in the triggering PR apply to the whole artifact. Invalid or unsafe inputs fail packaging before replacing the previous output, and the live deployment remains unchanged.
python3 tools/pages_preview.py build requires Git, network access, GITHUB_REPOSITORY, a read-only GITHUB_TOKEN with contents/PR access, and the Actions GITHUB_OUTPUT file. It fetches current immutable commits, renders the site into dist/, and exports the packaged preview list. python3 tools/pages_preview.py comment uses PAGE_URL and DEPLOYED_PREVIEWS from the successful deployment plus a token with PR write access to reconcile comments. Both commands run automatically in the workflow; local tests use temporary repositories and mocked API calls without publishing or commenting.
The website uses the exact Markdown renderer versions in site/requirements.txt during builds and native HTML/CSS/JavaScript in the browser. Browser checks reuse the existing locked media-test Chromium; see tests/README.md.
See CONTRIBUTING.md before adding or changing a skill. Keep each skill focused and independently usable, and update the catalog when publishing one.
Formatting requires Node.js and npm. CI uses Node.js 24 and Prettier 3.8.3:
npx --yes prettier@3.8.3 --check '**/*.{md,yml,yaml,json}' .prettierrcThe first invocation needs registry access unless that version is cached. CI also runs helper contracts, provenance checks, synthetic audit-tool tests, and browser/media integration described in tests/README.md. Agent behavior still needs separate verification as described in the contribution guide.
The skills and supporting tests are adapted from Agentic Skills. Bundled source records and third-party notices retain their upstream attribution.
MIT. Preserve any bundled third-party license notices and attribution.
The source adaptation review documents the additional design, motion, game, sound, and engineering sources reviewed on 2026-10-26, including material excluded from redistribution.
Browse the external material catalogues for per-skill source links, local paths, uses, licenses, and explicit "Unknown" provenance fields.