Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

upload-skill

Estrelas0

Forks0

Atualizado25 de março de 2026 às 20:29

Upload new or updated skill folders to the remote main branch, triggering the CI/CD pipeline to publish them as dedicated skill branches. Use this skill whenever the user wants to commit and push new or modified skills to the repository.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

chrishuffman5

chrishuffman5/skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	upload-skill
description	Upload new or updated skill folders to the remote main branch, triggering the CI/CD pipeline to publish them as dedicated skill branches. Use this skill whenever the user wants to commit and push new or modified skills to the repository.

upload-skill

Upload new or updated skill folders to the remote main branch, triggering the CI/CD pipeline to publish them as dedicated skill branches.

Invoking /upload-skill is an explicit grant of permission to commit and push to the remote main branch. Do not ask for additional confirmation — proceed directly.

Instructions

When the user invokes /upload-skill:

Ensure you are on the main branch. If not, switch to it.
Run git status to detect new or modified skill folders in the repo root. Skill folders are any root-level directories that are NOT reserved entries (.git, .github, .claude, .gitignore, CLAUDE.md, LICENSE, README.md).
Log which skill folder(s) will be uploaded (for the user's awareness, not as a confirmation prompt).
Update README.md — Regenerate the skills table in README.md at the repo root so it lists every skill folder currently in the repo (sorted alphabetically). Each row should have the skill name and its install command. Use the existing README.md format:
```
| skill-name | `git clone https://github.com/chrishuffman5/skills --branch skill-name skill-name` |
```
Keep the file header and installation instructions intact — only regenerate the table rows.
Stage the skill folder(s) and README.md — use git add <folder-name>/ README.md for each detected skill folder. Do not use git add -A or git add ..
Commit with the message format:
- Single skill: Add <skill-name> skill
- Updated skill: Update <skill-name> skill
- Multiple skills: Add <skill-name-1>, <skill-name-2> skills
Push to remote main: git push origin main
Confirm to the user that the push succeeded and that the GitHub Actions pipeline will automatically create/update the corresponding skill branch(es). Remind them they can install the skill with:
```
git clone https://github.com/chrishuffman5/skills --branch <skill-name> <skill-name>
```

Mais deste repositório

mesmo repositório

install-skill

chrishuffman5/skills

Install a skill from a remote git repository into the local .claude/skills/ directory. Use this skill whenever the user wants to install, add, or set up a new skill — e.g., "install the pdf skill", "add the remotion skill", "set up the xlsx skill". Also trigger when users reference installing skills by name or ask how to get a skill.

2026-03-270

design-md

chrishuffman5/skills

Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files

2026-03-270

enhance-prompt

chrishuffman5/skills

Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.

2026-03-270

react-components

chrishuffman5/skills

Converts Stitch designs into modular Vite and React components using system-level networking and AST-based validation.

2026-03-270

remotion-best-practices

chrishuffman5/skills

Best practices for Remotion - Video creation in React

2026-03-270

shadcn-ui

chrishuffman5/skills

Expert guidance for integrating and building applications with shadcn/ui components, including component discovery, installation, customization, and best practices.

2026-03-270

name	upload-skill
description	Upload new or updated skill folders to the remote main branch, triggering the CI/CD pipeline to publish them as dedicated skill branches. Use this skill whenever the user wants to commit and push new or modified skills to the repository.

upload-skill

Upload new or updated skill folders to the remote main branch, triggering the CI/CD pipeline to publish them as dedicated skill branches.

Invoking /upload-skill is an explicit grant of permission to commit and push to the remote main branch. Do not ask for additional confirmation — proceed directly.

Instructions

When the user invokes /upload-skill:

Ensure you are on the main branch. If not, switch to it.
Run git status to detect new or modified skill folders in the repo root. Skill folders are any root-level directories that are NOT reserved entries (.git, .github, .claude, .gitignore, CLAUDE.md, LICENSE, README.md).
Log which skill folder(s) will be uploaded (for the user's awareness, not as a confirmation prompt).
Update README.md — Regenerate the skills table in README.md at the repo root so it lists every skill folder currently in the repo (sorted alphabetically). Each row should have the skill name and its install command. Use the existing README.md format:
```
| skill-name | `git clone https://github.com/chrishuffman5/skills --branch skill-name skill-name` |
```
Keep the file header and installation instructions intact — only regenerate the table rows.
Stage the skill folder(s) and README.md — use git add <folder-name>/ README.md for each detected skill folder. Do not use git add -A or git add ..
Commit with the message format:
- Single skill: Add <skill-name> skill
- Updated skill: Update <skill-name> skill
- Multiple skills: Add <skill-name-1>, <skill-name-2> skills
Push to remote main: git push origin main
Confirm to the user that the push succeeded and that the GitHub Actions pipeline will automatically create/update the corresponding skill branch(es). Remind them they can install the skill with:
```
git clone https://github.com/chrishuffman5/skills --branch <skill-name> <skill-name>
```