New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Add Oliphaunt Extension

by f0rr0 in f0rr0/oliphaunt

Add, update, or remove an Oliphaunt PostgreSQL contrib or external extension, including source pins, build recipes, target support, SDK metadata, release products, carrier identities, and package…

MITAuto-check passedDatabases

Install Add Oliphaunt Extension

skills CLI
$ npx skills add f0rr0/oliphaunt --skill add-oliphaunt-extension -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install f0rr0/oliphaunt add-oliphaunt-extension --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/f0rr0/oliphaunt.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/add-oliphaunt-extension .claude/skills/add-oliphaunt-extension && rm -rf skills-src

Use ~/.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/

Facts

Skill name
add-oliphaunt-extension
GitHub stars
105
Token cost
~1.4k tokens
SKILL.md length
679 words
Files
2
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Add, update, or remove an Oliphaunt PostgreSQL contrib or external extension, including source pins, build recipes, target support, SDK metadata, release products, carrier identities, and package…

  • Works in 4 steps: Add or update source pins, checksums,… → The canonical target profiles in… → For an active public product, declare… → …
  • Extension catalog
  • SKILL.md covers Classify, Implement and Review
  • Calls bash

What it does

Add Oliphaunt Extension is an agent skill from f0rr0/oliphaunt. Add, update, or remove an Oliphaunt PostgreSQL contrib or external extension, including source pins, build recipes, target support, SDK metadata, release products, carrier identities, and package verification. Use whenever extension catalog, compatibility, packaging, or supported OS/runtime claims change.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Databases. It works with PostgreSQL. The repository describes itself as: Embedded Postgres inside your apps and tests. No Docker, Node.js, or server. As easy as SQLite. The licence is MIT.

When your agent uses it

  • Extension catalog
  • Supported OS/runtime claims change

Example prompts

  • “/add-oliphaunt-extension”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Add or update source pins, checksums, patches/dependency recipes, and Moon
  2. The canonical target profiles in src/extensions/contracts/extension-target-profiles.toml apply to every extension on main. A…
  3. For an active public product, declare the stable Cargo façade plus native,
  4. Regenerate the shared extension model

What it can do on your machine

Read from SKILL.md and the folder at commit 31b5803. 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

    Shell commands in SKILL.md call:

    • bash

    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.

Context cost

Add Oliphaunt Extension loads about 1.4k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 679 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from f0rr0/oliphaunt at commit 31b5803, republished under its MIT licence (© f0rr0). 679 words, ~1,420 tokens.

Download SKILL.mdSave it as .claude/skills/add-oliphaunt-extension/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
add-oliphaunt-extension
description
Add, update, or remove an Oliphaunt PostgreSQL contrib or external extension, including source pins, build recipes, target support, SDK metadata, release products, carrier identities, and package verification. Use whenever extension catalog, compatibility, packaging, or supported OS/runtime claims change.

Add Oliphaunt Extension

Make support claims fail closed. A runtime target existing does not prove an extension supports that target.

Classify

  • contrib: source is PostgreSQL 18. The SQL member belongs to the oliphaunt-extension-contrib-pg18 logical distribution at src/extensions/contrib/. It is not an independently versioned release product: its native and WASIX carriers belong to the corresponding runtime. A contrib member does not own a leaf VERSION, changelog, release.toml, tag, or registry identity.
  • external: source uses an immutable upstream commit, packaging versioning is upstream-bound, and runtime versions are compatibility metadata rather than release coupling. release.toml is the public-product boundary. Incomplete or blocked work stays on a branch and has no main-branch catalog state.

Keep the SQL extension name distinct from the release product id and upstream project name.

Implement

  1. Add or update source pins, checksums, patches/dependency recipes, and Moon metadata. For a public external extension, also maintain its product-local release.toml, VERSION, and empty first-release CHANGELOG.md. Every external extension must own upstream-license-data.json beside that metadata. After changing source or license pins, fetch the selected pinned sources and run moon run extensions:audit-license-sources to compare the actual upstream bytes. extensions:packaging-unit remains a cold-checkout packaging proof and does not silently expand its coverage when a local source cache exists. Freeze exactly the source identities and license/notice rows used by that extension, include only the referenced content-addressed blobs, and audit those bytes against the clean pinned checkout. Never put independently versioned extensions into one shared legal-data file. For a contrib member, update the canonical postgres18.toml inventory and the shared contrib distribution metadata; never create leaf release state. Check whether the upstream project operates an authoritative HTTPS Git mirror. When it does, record that reviewed endpoint as mirror_url and prove that it serves the exact pinned commit; never infer a mirror or use a community fork merely for availability.
  2. The canonical target profiles in src/extensions/contracts/extension-target-profiles.toml apply to every extension on main. A target-specific exception is branch work until its format and shipped behavior are implemented together; do not add status, promotion, or blocker metadata.
  3. For an active public product, declare the stable Cargo façade plus native, mobile, WASIX portable/AOT, npm, and Maven carriers actually required by the owning release product. Contrib members use the shared bundle carriers and retain exact nested member paths/checksums; public external extensions use their independent carriers. Let size-required Cargo package parts remain dynamic implementation carriers.
  4. Regenerate the shared extension model:
sh
bash src/extensions/tools/check-extension-model.sh --write

Source-pin, patch, recipe, compiler-input, or producer-code changes require the product-owned portable/AOT build. Version, changelog, registry coordinate, and target-profile edits are package-envelope changes.

Show full SKILL.md (258 more words)Show less
  1. Verify the model and release graph:
sh
bash src/extensions/tools/check-extension-model.sh --check
bash tools/release/release-check.sh

When source acquisition or mirror_url changes, also run the source-fetch fault suite, validate the real manifest, and perform one live exact-commit fetch from each newly declared endpoint. The canonical upstream must remain the durable origin and every transport must resolve to the same immutable pin.

  1. Build the exact extension artifacts for all declared targets. Require package-shape, archive safety, checksums, runtime load/create, restart, and dump/restore evidence where the target contract promises them. The exact-SHA CI lane must run src/extensions/tools/collect-wasix-evidence.sh against portable and host-AOT artifacts from that same workflow run. Only that collector may record wasix-full-lifecycle-v1; its immutable record must identify the exact commit, tree, workflow run, attempt, and job, and qualification must pass --require-current-evidence.
  2. Run a clean local-registry install for each ecosystem façade. For a contrib bundle, select at least two members and prove that only those nested members are staged even though one target carrier contains all contrib bytes. Also combine one contrib member with an independently versioned external member. Confirm target selection fetches only the expected carriers and an unsupported target fails with a useful error. Verify each carrier's derived license and notice profile; a passing profile check is not legal advice or certification of comprehensive legal compliance.

Review

Reject the change if a declared target lacks a produced artifact, an actual package lacks a declared identity, an external extension is runtime-version-coupled, or generated SDK metadata disagrees. Reject any promotion, blocker, deferred, planned, or unsupported extension state on main. Report upstream source identity separately from Oliphaunt package version.

© f0rr0, 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 1 other file in .codex/skills/add-oliphaunt-extension of f0rr0/oliphaunt.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 31b5803

Compare with similar skills

Add Oliphaunt Extension 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.

Add Oliphaunt Extension compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add Oliphaunt Extension this skillf0rr0/oliphaunt105—~1.4kAutomated safety check: PassMIT
Backend Test WorkerCorrectRoadH/OpenTickly306—~1.3kAutomated safety check: PassAGPL-3.0
Ef Core Migrationsjihadkhawaja/Egroo178—~673Automated safety check: PassApache-2.0
Diagnose Cloud SessionFreakStudioCN/mpy-hardware-extension118—~809Automated safety check: NotesCustom licence
DB AdminEliasOulkadi/shokunin114—~2kAutomated safety check: NotesMIT
Postgresql Table Designynulihao/AgentSkillOS61714 repos~4kAutomated safety check: PassNone

Similar skills

  • Backend Test Worker

    CorrectRoadH/OpenTickly

    Build and verify real-Postgres Go tests and thin transport smoke for tracking behavior.

    306 GitHub stars~1.3k tokensUpdated 5 days ago
    DatabasesAuto-check passed

  • Ef Core Migrations

    jihadkhawaja/Egroo

    Handle EF Core schema changes in Egroo. An agent skill from jihadkhawaja/Egroo.

    178 GitHub stars~673 tokensUpdated 6 mo ago
    DatabasesAuto-check passed

  • Diagnose Cloud Session

    FreakStudioCN/mpy-hardware-extension

    用户报告 Blockless 扩展在云端实测时出问题（卡死/灰屏/跳步/构建失败），但本地复现不了、日志不在本地文件里时，用这个从云端托管数据库拉真实 session 定位症状与根因 / Use when a user reports an in-product Blockless bug from live cloud-backend testing and the real session…

    118 GitHub stars~809 tokensUpdated 9 days ago
    DatabasesAuto-check: notes

  • DB Admin

    EliasOulkadi/shokunin

    PostgreSQL database administration — backup/restore (pgdump, PITR, WAL archiving), health monitoring (connections, bloat, cache hit ratio, dead tuples), connection pooling (PgBouncer), replication…

    114 GitHub stars~2k tokensUpdated 2 days ago
    DatabasesAuto-check: notes

  • Postgresql Table Design

    ynulihao/AgentSkillOS

    Design a PostgreSQL-specific schema. An agent skill from ynulihao/AgentSkillOS.

    617 GitHub starsUsed in 14 repos~4k tokens
    DatabasesAuto-check passed

  • Postgres Patterns

    ThibautBaissac/rails_ai_agents

    PostgreSQL database patterns for query optimization, schema design, indexing, and security.

    665 GitHub starsUsed in 7 repos~922 tokens
    DatabasesAuto-check passed

More from f0rr0/oliphaunt

  • Release Oliphaunt

    f0rr0/oliphaunt

    Prepare, audit, bootstrap, publish, verify, or recover Oliphaunt releases across GitHub, crates.io, npm, Maven Central, and SwiftPM.

    105 GitHub stars~4k tokensUpdated today
    Auto-check passed

  • Write Oliphaunt Docs

    f0rr0/oliphaunt

    Write, rewrite, audit, or redesign Oliphaunt developer documentation.

    105 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Qualify Oliphaunt Change

    f0rr0/oliphaunt

    Select, run, and diagnose Oliphaunt local and GitHub CI qualification for code, package, extension, SDK, policy, workflow, or release changes.

    105 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Add Oliphaunt Extension

What does Add Oliphaunt Extension do?

Add, update, or remove an Oliphaunt PostgreSQL contrib or external extension, including source pins, build recipes, target support, SDK metadata, release products, carrier identities, and package…. Add Oliphaunt Extension is an agent skill from f0rr0/oliphaunt. Add, update, or remove an Oliphaunt PostgreSQL contrib or external extension, including source pins, build recipes, target support, SDK metadata, release products, carrier identities, and package verification.

When should I use Add Oliphaunt Extension?

Add Oliphaunt Extension fits situations like: extension catalog; supported OS/runtime claims change.

How do I install Add Oliphaunt Extension in Claude Code?

Run `npx skills add f0rr0/oliphaunt --skill add-oliphaunt-extension -a claude-code`. Or copy the skill folder (.codex/skills/add-oliphaunt-extension in f0rr0/oliphaunt) into .claude/skills/add-oliphaunt-extension in your project. Claude Code loads it when a task matches its description.

How do I install Add Oliphaunt Extension in Codex?

Run `npx skills add f0rr0/oliphaunt --skill add-oliphaunt-extension -a codex`. Or copy the skill folder (.codex/skills/add-oliphaunt-extension in f0rr0/oliphaunt) into .agents/skills/add-oliphaunt-extension in your project. Codex loads it when a task matches its description.

Can I use Add Oliphaunt Extension 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 f0rr0/oliphaunt --skill add-oliphaunt-extension -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-oliphaunt-extension, .gemini/skills/add-oliphaunt-extension, .github/skills/add-oliphaunt-extension and .opencode/skills/add-oliphaunt-extension in your project.

What does Add Oliphaunt Extension need to run?

Going by SKILL.md and its folder, Add Oliphaunt Extension needs the command-line tools its instructions call (bash).

Does Add Oliphaunt Extension 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 Add Oliphaunt Extension 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. Review the folder before installing.

What licence does Add Oliphaunt Extension use?

Add Oliphaunt Extension is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Add Oliphaunt Extension use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Add Oliphaunt Extension?

Skills that share tags, products or a category with Add Oliphaunt Extension: Backend Test Worker (CorrectRoadH/OpenTickly, 306 stars), Ef Core Migrations (jihadkhawaja/Egroo, 178 stars), Diagnose Cloud Session (FreakStudioCN/mpy-hardware-extension, 118 stars) and DB Admin (EliasOulkadi/shokunin, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Oliphaunt Extension?

f0rr0 (a GitHub user) maintains it in f0rr0/oliphaunt, which has 105 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.

Source: f0rr0/oliphaunt on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.