Run any Skill in Manus with one click

buildskill

Stars5

Forks3

UpdatedJuly 13, 2026 at 20:14

Create and validate skills for forge modules. USE WHEN create skill, new skill, write skill, validate skill, check skill, skill structure, skill conventions.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

N4M3Z

N4M3Z/forge-core

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

File Explorer

11 files

SKILL.md

readonly

name	BuildSkill
version	0.1.0
description	Create and validate skills for forge modules. USE WHEN create skill, new skill, write skill, validate skill, check skill, skill structure, skill conventions.

BuildSkill

Create and validate skills following forge conventions. Skills are markdown files (SKILL.md) with YAML frontmatter that teach AI coding tools new capabilities. Load only the companion relevant to the current task.

Workflow Routing

Workflow	Trigger	Companion
Create	"create a skill", "new skill", "write a skill"	@CreateWorkflow.md
Validate	"validate skill", "check skill structure"	@ValidateWorkflow.md

Topics

Topic	Companion
SKILL.md structure, frontmatter, body layout, naming	@SkillStructure.md
Dynamic context injection (`!`): open a Claude skill with live state	@DynamicContextInjection.md
Multi-provider routing via `defaults.yaml`	@MultiProviderRouting.md
Wrapping a CLI tool in a skill	@CliToolIntegration.md
Platform-agnostic writing — no placeholders or `/` prefix	@PlatformAgnostic.md
User-config schema for AI-first artifacts (autoMode mirror)	@UserConfigSchema.md
Claude-only features: `@` refs, skill discovery, `allowed-tools`	@ClaudeSkill.md
When to author a per-skill INSTALL.md	@SkillInstallation.md

Red Flags

Thought	Reality
"Put argument-hint in SKILL.md frontmatter"	Obsidian Linter reformats frontmatter. Provider-specific fields go in SKILL.yaml.
"Use `/SkillName` inside a skill body"	Slashes are user-facing invocation syntax, not internal references.
"Skip the `USE WHEN` clause"	Claude uses it to route. Missing trigger = skill never fires.
"Leave a stub section as a placeholder"	Skill bodies are plain prose. Delete empty sections, don't scaffold them.
"Inline every example in the SKILL.md"	SKILL.md should stay slim. Move static reference material to companion files.
"Skill directory can have any name"	Directory name must match the `name:` frontmatter field exactly.
"Put a `!` injection in a companion file"	`!` runs only in the SKILL.md body; in a companion it renders as literal text. See @ClaudeSkill.md.
"Inject a secret value with `!` (e.g. `pass show`)"	Injection lands in the transcript. Inject structure/status (names, vault list), never secret values.
"It ran in my sandbox, so the probe is done"	Your sandbox has tooling (uv, personal paths, aliases) the target machine lacks — resolve interpreters at preflight and assume a clean environment.

Constraints

Every skill MUST have name: and description: in frontmatter
Description MUST include USE WHEN trigger phrases
PascalCase for multi-word skill names, natural case for single words
Skill directory name must match the name: field
Prefer one SKILL.md per skill — extract reference material into companion files when body exceeds ~150 lines or contains dense static data

Sources

More from this repository

same repository

forgeskill

N4M3Z/forge-core

Create, validate, evaluate, and iterate skills for forge modules. USE WHEN create skill, new skill, write skill, validate skill, check skill, skill structure, skill conventions, test a skill, run skill evals, benchmark a skill, skill not triggering, optimize skill description. Not for adopting community skills (AdoptArtifact) or shipping artifacts downstream (PublishArtifact).

2026-07-135

buildrule

N4M3Z/forge-core

Create, validate, or place behavioral rules in forge modules. USE WHEN create rule, new rule, write rule, capture rule, add a rule, graduate a correction or convention to a rule, validate rule, rule conventions, where does this rule belong, or the user runs /Rule.

2026-07-135

initproject

N4M3Z/forge-core

Scaffold a workshop project: a VCS spine (git + jj colocate + entire + forge hooks), the private/public/assets flow layout with a .tlp manifest, a .claude/ that mounts the knowledge vault, and on-demand satellites (vault folder-note, data dir, private remote). USE WHEN starting a new project, initializing a folder for work, adding a vault note or data dir or remote to a project, archiving a project, or the user runs `project` / `atlas`.

2026-07-135

brainstorming

N4M3Z/forge-core

Collaborative ideation before implementation — explore context, clarify intent, propose approaches. USE WHEN starting creative work, new features, design decisions, or modifying behavior.

2026-07-135

designspec

N4M3Z/forge-core

Write a formal design spec from brainstorming output or requirements. USE WHEN design approved, write spec, formalize design, spec document.

2026-07-135

executeplan

N4M3Z/forge-core

Execute an implementation plan inline — task by task in a single session — then finish the work: verify, present integration options (merge, PR, keep, discard), and clean up the workspace. USE WHEN executing plan, run plan, implement plan, inline execution, implementation complete, deciding merge strategy, finishing a feature branch or workspace.

2026-07-135

BuildSkill

Workflow Routing

Workflow

Trigger

Companion

Create

"create a skill", "new skill", "write a skill"

@CreateWorkflow.md

Validate

"validate skill", "check skill structure"

@ValidateWorkflow.md

Topics

Topic

Companion

SKILL.md structure, frontmatter, body layout, naming

@SkillStructure.md

Dynamic context injection (!): open a Claude skill with live state

@DynamicContextInjection.md

Multi-provider routing via defaults.yaml

@MultiProviderRouting.md

Wrapping a CLI tool in a skill

@CliToolIntegration.md

Platform-agnostic writing — no placeholders or / prefix

@PlatformAgnostic.md

User-config schema for AI-first artifacts (autoMode mirror)

@UserConfigSchema.md

Claude-only features: @ refs, skill discovery, allowed-tools

@ClaudeSkill.md

When to author a per-skill INSTALL.md

@SkillInstallation.md

Red Flags

Thought

Reality

"Put argument-hint in SKILL.md frontmatter"

Obsidian Linter reformats frontmatter. Provider-specific fields go in SKILL.yaml.

"Use /SkillName inside a skill body"

Slashes are user-facing invocation syntax, not internal references.

"Skip the USE WHEN clause"

Claude uses it to route. Missing trigger = skill never fires.

"Leave a stub section as a placeholder"

Skill bodies are plain prose. Delete empty sections, don't scaffold them.

"Inline every example in the SKILL.md"

SKILL.md should stay slim. Move static reference material to companion files.

"Skill directory can have any name"

Directory name must match the name: frontmatter field exactly.

"Put a ! injection in a companion file"

! runs only in the SKILL.md body; in a companion it renders as literal text. See @ClaudeSkill.md.

"Inject a secret value with ! (e.g. pass show)"

Injection lands in the transcript. Inject structure/status (names, vault list), never secret values.

"It ran in my sandbox, so the probe is done"

Your sandbox has tooling (uv, personal paths, aliases) the target machine lacks — resolve interpreters at preflight and assume a clean environment.

Constraints

Every skill MUST have name: and description: in frontmatter

Description MUST include USE WHEN trigger phrases

PascalCase for multi-word skill names, natural case for single words

Skill directory name must match the name: field

Prefer one SKILL.md per skill — extract reference material into companion files when body exceeds ~150 lines or contains dense static data

Sources