Run any Skill in Manus with one click

skill-notes

Stars5

Forks0

UpdatedJuly 2, 2026 at 17:09

Standing preferences and constraints for evaluating, importing, or recommending skills. Use alongside import-external-skill when assessing external skill sets or proposing new skills.

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

timmo001

timmo001/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

SKILL.md

readonly

name	skill-notes
description	Standing preferences and constraints for evaluating, importing, or recommending skills. Use alongside import-external-skill when assessing external skill sets or proposing new skills.

Skill Notes

Consult these notes when evaluating external skills for import, recommending skills, or proposing new ones.

Testing

Do not use TDD, red-green-refactor, or test-first workflows.
Tests are verification tools, not design drivers.
Skip or flag any skill whose core workflow is TDD or test-first.
If an otherwise useful skill includes TDD content, note the conflict and offer to adapt with the TDD parts removed.

Issues and Planning

The user writes their own issues, especially in shared repos.
Skip skills that automate issue creation, breakdown-to-issues, or PRD-to-tickets workflows.

More from this repository

same repository

staged-implementation

timmo001/dotfiles

Execute broad changes one coherent, independently verifiable stage at a time. Use when work spans multiple independently reviewable changes, or when contracts, producer-consumer migrations, generated artefacts, or release packaging create an ordered multi-stage rollout; skip small single-purpose changes.

2026-07-105

git-commit

timmo001/dotfiles

Commit workflow using the dot git-commit gateway in the maintainer's concise one-line style. Use only after the user explicitly requests a commit or push, including /commit or /commit-push. Never infer repeat authorisation from an earlier commit or push; never run raw git commit.

2026-07-105

git-context

timmo001/dotfiles

Patterns for working with git branches, remotes, diffs against the default branch, and rebases. Use when resolving rebase conflicts, continuing interactive rebases, amending commits, or any git operation that would open an interactive editor.

2026-07-105

research

timmo001/dotfiles

Investigate a topic against primary sources and return cited findings, comparing credible maintainer and contributor perspectives when judgement is involved. Use when the user wants a topic researched, docs, API, or spec facts gathered, an external library or GitHub behaviour verified, competing views compared, or reading legwork delegated to a background agent.

2026-07-105

ask-questions-if-underspecified

timmo001/dotfiles

Ask minimal clarifying questions only when ambiguity materially changes implementation. Use for routine underspecification; do not use for user-requested light or full grilling, plan stress-testing, or broad design interviews.

2026-07-105

grill-questions

timmo001/dotfiles

Stress-test a plan or proposed change through focused one-question-at-a-time grilling, with light and full intensity. Use when the user says grill, grill me, grill me lightly, ask me a couple of questions, stress-test this plan, or wants question-led scrutiny before planning.

2026-07-105

Run any Skill with one click