How do I install the New skill?

Run npx skillmds@latest add liriliri/new in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the New skill do?

Create a new Tinker plugin from the template It is listed under Coding & Dev Tools on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with New?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

liriliri (@liriliri) published this skill. Their other Agent Skills are listed on their SkillMD profile.

New by liriliri — Agent Skill

Name: New
Author: liriliri

File contents

New Plugin

Create a new Tinker plugin from scratch.

Arguments

plugin-name: kebab-case name without the tinker- prefix (e.g., base64, color-picker)
description: optional short description in English

Steps

1. Find similar existing plugins

List existing plugins and check if any are functionally similar to the new one:

ls -d tinker-*/

If a similar plugin exists, ask the user whether to copy it as the base instead of tinker-template. Use the user's choice as the copy source in the next step.

2. Determine plugin type

Ask the user: does this plugin need Node.js/Electron APIs (file system, OS info, native dialogs beyond tinker.*, etc.)? If yes → advanced (with src/preload/ and src/renderer/). If no → basic (flat src/ layout).

3. Copy source

cp -r tinker-<source> tinker-<plugin-name>

Where <source> is either the similar plugin chosen by the user or tinker-template.

4. Update `package.json`

Edit tinker-<plugin-name>/package.json:

name → "tinker-<plugin-name>"
description → "<Description> Plugin for TINKER"
tinker.name → Title Case English name
tinker.description → short English description of what the plugin does
tinker.icon → "icon.png"
tinker.locales.zh-CN.name → Chinese name (ask if unclear)
tinker.locales.zh-CN.description → Chinese description

Basic plugin — simplify scripts and paths:

Replace dev / build with single vite commands (no concurrently)
Change tinker.main to "dist/index.html"
Remove tinker.preload

If the source is tinker-template, also restructure the directory:

mv src/renderer/* src/
rm -rf src/renderer src/preload

Then update import paths in index.html and all files under src/ — replace any src/renderer/ references with src/, and fix relative import paths affected by the directory change (e.g. ../../../share/ → ../../share/).

Advanced plugin — keep template scripts as-is, only update name/description.

Also remind the user: icon.png must be replaced with a real icon (200×200 px).

5. Build test

cd tinker-<plugin-name> && npm run build

Fix any TypeScript or build errors before finishing.

6. Stop — do not implement features

The scaffold is complete. Do not modify App.tsx, store.ts, i18n files, or any other source files to implement the plugin's actual functionality. Leave all template content as-is and inform the user that the scaffold is ready for them to implement.

---name: newdescription: Create a new Tinker plugin from the template---# New PluginCreate a new Tinker plugin from scratch.## Arguments- `plugin-name`: kebab-case name without the `tinker-` prefix (e.g., `base64`, `color-picker`)- `description`: optional short description in English## Steps### 1. Find similar existing pluginsList existing plugins and check if any are functionally similar to the new one:```bashls -d tinker-*/```If a similar plugin exists, ask the user whether to copy it as the base instead of `tinker-template`. Use the user's choice as the copy source in the next step.### 2. Determine plugin typeAsk the user: does this plugin need Node.js/Electron APIs (file system, OS info, native dialogs beyond `tinker.*`, etc.)? If yes → **advanced** (with `src/preload/` and `src/renderer/`). If no → **basic** (flat `src/` layout).### 3. Copy source```bashcp -r tinker-<source> tinker-<plugin-name>```Where `<source>` is either the similar plugin chosen by the user or `tinker-template`.### 4. Update `package.json`Edit `tinker-<plugin-name>/package.json`:- `name` → `"tinker-<plugin-name>"`- `description` → `"<Description> Plugin for TINKER"`- `tinker.name` → Title Case English name- `tinker.description` → short English description of what the plugin does- `tinker.icon` → `"icon.png"`- `tinker.locales.zh-CN.name` → Chinese name (ask if unclear)- `tinker.locales.zh-CN.description` → Chinese description**Basic plugin** — simplify scripts and paths:- Replace `dev` / `build` with single `vite` commands (no `concurrently`)- Change `tinker.main` to `"dist/index.html"`- Remove `tinker.preload`If the source is `tinker-template`, also restructure the directory:```bashmv src/renderer/* src/rm -rf src/renderer src/preload```Then update import paths in `index.html` and all files under `src/` — replace any `src/renderer/` references with `src/`, and fix relative import paths affected by the directory change (e.g. `../../../share/` → `../../share/`).**Advanced plugin** — keep template scripts as-is, only update name/description.Also remind the user: **`icon.png` must be replaced** with a real icon (200×200 px).### 5. Build test```bashcd tinker-<plugin-name> && npm run build```Fix any TypeScript or build errors before finishing.### 6. Stop — do not implement featuresThe scaffold is complete. **Do not** modify `App.tsx`, `store.ts`, i18n files, or any other source files to implement the plugin's actual functionality. Leave all template content as-is and inform the user that the scaffold is ready for them to implement.

Frequently asked questions

New