Pluginstaller

CommunityPopular

am-will

pluginstaller

Add a Codex plugin from a GitHub repo to a repo or personal marketplace using the current Codex plugin layout and marketplace metadata.

Overview

Publisher	am-will
Repository	`codex-skills`
Skill name	`pluginstaller`
Stars	1K
Forks	60
Bundled files	2
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by am-will on GitHub. Read the source before you install it.

Installation

Install the Pluginstaller AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/am-will/codex-skills.git /tmp/codex-skills
mkdir -p .claude/skills
cp -r /tmp/codex-skills/skills/pluginstaller .claude/skills/pluginstaller

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Pluginstaller in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Pluginstaller on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Pluginstaller is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Pluginstaller

Use when the user gives a GitHub repo for a Codex plugin and wants it available in Codex.

Follow the current Codex plugin docs. Do not invent alternate install flows.

Inputs

GitHub repo URL or owner/repo
Install scope: repo or personal
If the repo contains more than one plugin root, ask which plugin folder to install.

Workflow

If the user does not specify whether the plugin should be repo-scoped or personal, stop and ask.
Fetch the repo and locate the plugin root by finding .codex-plugin/plugin.json.
Read .codex-plugin/plugin.json and validate the canonical structure:
- name, version, and description should exist.
- Bundled paths such as skills, apps, and mcpServers should be relative to the plugin root and start with ./.
- Only plugin.json should live inside .codex-plugin/.
Prefer the built-in @plugin-creator skill when the task is to scaffold a new local plugin or add an existing local plugin to a marketplace. Use the manual path below when you are wiring up a repo the user already provided.
Copy the entire plugin directory, not just SKILL.md, into a marketplace-visible location. Default to the documented standard locations unless the repo already uses a different valid marketplace-relative path:
- repo: $CWD/plugins/<plugin-name> and $CWD/.agents/plugins/marketplace.json
- personal: ~/.codex/plugins/<plugin-name> and ~/.agents/plugins/marketplace.json
Preserve the full bundle at the plugin root, including sibling skills/, .app.json, .mcp.json, assets/, and any other plugin files. Do not move those files under .codex-plugin/.
Create or update the marketplace file with the documented schema:
- top-level marketplace name
- optional interface.displayName
- plugin entry name
- source.source = "local"
- source.path relative to the marketplace root:
  - repo: ./plugins/<plugin-name>
  - personal: ./.codex/plugins/<plugin-name>
- policy.installation
- policy.authentication
- category
Use marketplace values that match the docs unless the user says otherwise:
- policy.installation = "AVAILABLE"
- policy.authentication = "ON_INSTALL"
- category from interface.category when present, otherwise Productivity
Merge into any existing marketplace file instead of replacing it.
Restart Codex and verify the plugin appears in /plugins.
Report the runtime behavior accurately:

The marketplace entry points to the source plugin directory.
Codex installs the plugin into ~/.codex/plugins/cache/<marketplace>/<plugin>/<version>/.
For local plugins, the installed cache version is local.
Plugin enabled or disabled state is stored in ~/.codex/config.toml.

Rules

Prefer the terms repo marketplace and personal marketplace over workspace and global.
Do not present copying into plugins/ as the complete install. The marketplace entry is what makes the plugin discoverable in Codex.
Do not flatten or rename the plugin bundle.
Keep the plugin name stable and consistent across folder, manifest, and marketplace entry.
Keep manifest and marketplace paths relative and ./-prefixed where the docs require it.
Treat the documented repo and personal plugin directories as defaults, not absolute requirements, as long as the marketplace source.path remains valid and stays inside the marketplace root.
If the repo already ships a marketplace file, prefer it as the source of truth for marketplace ordering and metadata, and only add or update the plugin entry that is needed.
If the manifest is missing required basics or uses invalid root-relative paths, fix the plugin structure before claiming installation is complete.

Scope guide

Use repo when the plugin should live with one repo or be shared through that repo's marketplace. Use personal when the plugin should be available from the user's own Codex setup across projects.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB
references/install-scope.md1 KB

Frequently asked questions

What does the Pluginstaller AI skill do?

Add a Codex plugin from a GitHub repo to a repo or personal marketplace using the current Codex plugin layout and marketplace metadata.

Why use Pluginstaller on TypingMind?

Because you install it once and use it with any model. Pluginstaller is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Pluginstaller in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/am-will/codex-skills/tree/main/skills/pluginstaller. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Pluginstaller?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Pluginstaller?

As many as you like. As long as a model supports skills, you can use Pluginstaller with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Pluginstaller AI skill free?

It is published on GitHub by am-will. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Jpa Patterns

affaan-m

CommunityPopular

Patrones JPA/Hibernate para diseño de entidades, relaciones, optimización de consultas, transacciones, auditoría, indexación, paginación y pooling en Spring Boot.

Kotlin Patterns

Patrones idiomáticos de Kotlin, buenas prácticas y convenciones para construir aplicaciones Kotlin robustas, eficientes y mantenibles con coroutines, null safety y builders de DSL.

Kotlin Testing

Patrones de pruebas Kotlin con Kotest, MockK, pruebas de coroutines, pruebas basadas en propiedades y cobertura con Kover. Sigue la metodología TDD con prácticas idiomáticas de Kotlin.

Laravel Patterns

Patrones de arquitectura Laravel, routing/controladores, Eloquent ORM, capas de servicio, colas, eventos, caché y API resources para aplicaciones en producción.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Pluginstaller

Inputs

Workflow

Rules

Scope guide

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now