Run any Skill in Manus with one click

crafting-skills

Stars17

Forks2

UpdatedJuly 25, 2026 at 12:16

Use when creating or updating skills in `~/.config/ai/skills`, especially when a `SKILL.md` has a weak trigger, tangled structure, poor steering, or bloated wording.

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

l-lin

l-lin/dotfiles

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

3 files

SKILL.md

readonly

name	crafting-skills
description	Use when creating or updating skills in `~/.config/ai/skills`, especially when a `SKILL.md` has a weak trigger, tangled structure, poor steering, or bloated wording.
disable-model-invocation	true

REQUIRED SUB-SKILL: Use clear-writing for the final rewrite.

Read the target SKILL.md and any linked references. Do not edit yet.
Interview the user using ask-user-question tool before changing anything. Cover all four: trigger, structure, steering, pruning. Use references/SKILL-CHECKLIST.md.
Decide the smallest honest move: create, rewrite, split, merge, or delete. Ask before split, merge, or delete.
Rewrite for the chosen path.
- Trigger: choose user-invoked vs model-invocable on purpose. For user-only skills, set disable-model-invocation: true.
- Structure: keep SKILL.md tiny. Use numbered steps. Move branch-only reference into supporting files.
- Steering: pick a few leading words and repeat them consistently.
- Pruning: delete sediment, duplication, stale guidance, and no-ops.
Bias toward rewrite-after-audit when the old skill is bloated or tangled. Patch in place only when the structure is already sound.
Hand off verification. Name the pressure scenarios that should fail without the skill, the deletion tests that prove each paragraph earns its keep, and the next check to run. Do not claim the skill works without evidence.

More from this repository

same repository

kibana-elasticsearch

l-lin/dotfiles

Use when querying Elasticsearch through the Kibana console proxy, especially for log investigations, field-based filtering, or error triage from job or application logs.

2026-07-2517

devils-advocate

l-lin/dotfiles

Use when pressure-testing a plan, architecture, code change, or AI-generated proposal before committing, especially when hidden assumptions, production risks, or failure modes may be underexplored.

2026-07-2517

datadog-pup

l-lin/dotfiles

Use when interacting with Datadog resources using the `pup` CLI, especially for APM traces, metrics, monitors, notebooks, and synthetic tests.

2026-07-2517

code-simplifier

l-lin/dotfiles

Use when simplifying recently touched code without changing behavior, especially when asked to "simplify code", "clean up code", "refactor for clarity", or "improve readability".

2026-07-2517

ingest-url

l-lin/dotfiles

Ingest a URL into the patient account wiki. Use when the user provides a URL (Atlassian/Confluence, web articles, documentation) and wants to add it to their research wiki. Handles fetching, markdown conversion, asset extraction, and runs the full wiki ingest workflow. Triggers on "ingest <url>", "add this to the wiki", or when user shares a URL in the context of wiki research.

2026-07-2417

journal

l-lin/dotfiles

Use at session start, after context compaction, and before session end. Owns session journals in `.sandbox/journals/`: when to create one, what prior context to read, what to log, and how to leave a resumable handoff

2026-07-1117

name	crafting-skills
description	Use when creating or updating skills in `~/.config/ai/skills`, especially when a `SKILL.md` has a weak trigger, tangled structure, poor steering, or bloated wording.
disable-model-invocation	true

REQUIRED SUB-SKILL: Use clear-writing for the final rewrite.

Read the target SKILL.md and any linked references. Do not edit yet.
Interview the user using ask-user-question tool before changing anything. Cover all four: trigger, structure, steering, pruning. Use references/SKILL-CHECKLIST.md.
Decide the smallest honest move: create, rewrite, split, merge, or delete. Ask before split, merge, or delete.
Rewrite for the chosen path.
- Trigger: choose user-invoked vs model-invocable on purpose. For user-only skills, set disable-model-invocation: true.
- Structure: keep SKILL.md tiny. Use numbered steps. Move branch-only reference into supporting files.
- Steering: pick a few leading words and repeat them consistently.
- Pruning: delete sediment, duplication, stale guidance, and no-ops.
Bias toward rewrite-after-audit when the old skill is bloated or tangled. Patch in place only when the structure is already sound.
Hand off verification. Name the pressure scenarios that should fail without the skill, the deletion tests that prove each paragraph earns its keep, and the next check to run. Do not claim the skill works without evidence.