Automated summary
Generates a new codeup action file in the actions/ directory with a filter step and an apply step, based on the condition and steps the user describes.
Strengths
- Provides a complete defineAction-based template with meta, filter and apply fields
- Documents the utils API (file system, JSON, package.json) through concise method tables
- Includes common filter patterns such as file existence, any-extension matching, and dependency checks
Limitations
- Assumes an existing codeup project with an actions/ directory and the codeup package installed
- The common-filter section is truncated, and utilities cover only file system, JSON and package.json (nothing for network or shell commands)
- Gives no guidance on validating or testing the generated action
Use it when you need to scaffold a new codeup action with a trigger condition and defined steps.
Avoid it outside a codeup project or when you need a standalone script that is not part of codeup's action system.
Security analysis
SafeThe skill only provides templates and guidance for generating codeup action files. It does not instruct the agent to run destructive commands, exfiltrate data, or use obfuscated payloads. Examples include file removal and package script execution, but only as generated action code for legitimate project migrations.
No concerns found
How this analysis is madeExamples
Create a codeup action named migrate-eslintrc that only runs when .eslintrc exists and .eslintrc.json does not, and writes the config out as JSON.Make a codeup action add-prettier that filters on a package.json existing and adds prettier as a dev dependency plus a format script.Add a codeup action called warn-missing-tsconfig that runs only when tsconfig.json is missing and appends a note to a TODO file.name: codeup-action description: Create a new codeup action with filter and apply steps argument-hint: "[action-name]"
Codeup Action Skill
Create a new codeup action based on user-provided filter and steps.
Instructions
When user provides:
- filter: Condition for when the action should run
- steps: What the action should do
Generate a new action file in actions/ directory.
Action Structure
import { defineAction } from "codeup";
export default defineAction({
meta: {
name: "action-name", // kebab-case name
description: "Description", // Short description of what it does
date: "YYYY-MM-DD", // Today's date
},
async filter({ utils }) {
// Return true if action should run, false otherwise
return await utils.exists("some-file");
},
async apply({ utils }) {
// Perform the action steps
},
});
Available Utilities (utils)
File System
| Method | Description |
| ------------------------------ | ------------------------------------------------------------------------------------ |
| resolve(path) | Resolve path relative to cwd |
| exists(path) | Check if file/directory exists |
| existsWithAnyExt(path) | Check if file exists with any extension (e.g., .eslintrc matches .eslintrc.json) |
| read(path) | Read file contents as string |
| readLines(path) | Read file as array of lines |
| write(path, contents, opts?) | Write file. Options: { skipIfExists?: boolean, log?: boolean } |
| remove(path) | Remove file or directory |
| findUp(name) | Find file in cwd or parent directories |
| update(path, fn) | Read file, transform with fn, write back |
| append(path, contents) | Append to file |
JSON
| Method | Description |
| ----------------------------- | ---------------------------------------- |
| readJSON(path) | Read and parse JSON file |
| writeJSON(path, obj, opts?) | Write object as JSON |
| updateJSON<T>(path, fn) | Read JSON, transform with fn, write back |
Package.json
| Method | Description |
| ------------------------------- | --------------------------------------------- |
| readPackageJSON() | Read closest package.json |
| updatePackageJSON(fn) | Update package.json with transformer function |
| addDependency(name) | Add dependency (string or array) |
| addDevDependency(name) | Add dev dependency (string or array) |
| removeDependency(name) | Remove dependency |
| detectPackageManager() | Detect npm/yarn/pnpm/bun |
| runPackageManagerCommand(cmd) | Run command with detected package manager |
| runScript(script) | Run package.json script |
Common Filter Patterns
// File exists
await utils.exists("tsconfig.json");
// File with any extension exists
await utils.existsWithAnyExt(".eslintrc");
// File exists AND another doesn't
(await utils.exists("old.config")) && !(await utils.exists("new.config"));
// Check package.json for dependency
const pkg = await utils.readPackageJSON();
return !!pkg?.devDependencies?.["some-package"];
// Check package.json scripts
const pkg = await utils.readPackageJSON();
const scripts = Object.values(pkg?.scripts || {}) as string[];
return scripts.some((s) => s.includes("some-command"));
Common Apply Patterns
// Remove files
await utils.remove(".oldconfig");
await utils.remove(".oldignore");
// Write new config (skip if exists)
await utils.write("new.config.json", JSON.stringify({ key: "value" }, null, 2), {
skipIfExists: true,
});
// Update package.json scripts
await utils.updatePackageJSON((pkg) => {
for (const name in pkg.scripts) {
if (pkg.scripts[name]?.includes("old-cmd")) {
pkg.scripts[name] = pkg.scripts[name].replace("old-cmd", "new-cmd");
}
}
});
// Add/remove dependencies
await utils.addDevDependency("new-package@^1.0.0");
await utils.removeDependency("old-package");
// Update JSON config
await utils.updateJSON<SomeType>("config.json", (config) => {
delete config.oldOption;
config.newOption = true;
});
// Run script after changes
await utils.runScript("lint:fix");
Example Actions
Migration Action (eslint-flat style)
import { defineAction } from "codeup";
export default defineAction({
meta: {
name: "migrate-config",
description: "Migrate from old config to new config",
date: "2026-01-29",
},
async filter({ utils }) {
return (
(await utils.existsWithAnyExt(".oldrc")) && !(await utils.existsWithAnyExt("new.config"))
);
},
async apply({ utils }) {
// Read old config
const oldConfig = await utils.readJSON(".oldrc");
// Write new config
await utils.write("new.config.mjs", getTemplate(oldConfig));
// Remove old files
await utils.remove(".oldrc");
await utils.remove(".oldignore");
// Update dependencies
await utils.addDevDependency("new-tool@^2.0.0");
await utils.removeDependency("old-tool");
},
});
Tool Switch Action (tsgo style)
import { defineAction } from "codeup";
export default defineAction({
meta: {
name: "switch-tool",
description: "Switch from tool-a to tool-b",
date: "2026-01-29",
},
async filter({ utils }) {
const pkg = await utils.readPackageJSON();
return !!pkg?.devDependencies?.["tool-a"];
},
async apply({ utils }) {
// Update scripts
await utils.updatePackageJSON((pkg) => {
for (const name in pkg.scripts) {
if (pkg.scripts[name]?.includes("tool-a")) {
pkg.scripts[name] = pkg.scripts[name].replace("tool-a", "tool-b");
}
}
});
// Swap dependencies
await utils.removeDependency("tool-a");
await utils.addDevDependency("tool-b@latest");
},
});
Task
- Ask for action name if not provided
- Ask for filter condition (when should this action run?)
- Ask for steps (what should the action do?)
- Determine appropriate directory under
actions/(useactions/unjs/for unjs-related actions) - Generate the action file with proper structure
- Use today's date for the
meta.datefield
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/create-a-codeup-action-mma3js14/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/create-a-codeup-action-mma3js14' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-a-codeup-action-mma3js14/download' --output '.skill-downloads/create-a-codeup-action-mma3js14/SKILL.md.part' && mv '.skill-downloads/create-a-codeup-action-mma3js14/SKILL.md.part' '.skill-downloads/create-a-codeup-action-mma3js14/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/create-a-codeup-action-mma3js14/SKILL.md' && test -s '.skill-downloads/create-a-codeup-action-mma3js14/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/codeup-action' && cp -R '.skill-downloads/create-a-codeup-action-mma3js14' '.claude/skills/codeup-action'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/create-a-codeup-action-mma3js14'openskills read 'create-a-codeup-action-mma3js14'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/create-a-codeup-action-mma3js14/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.