القائمة
Minimal reference skill bundled with the hello-plugin example. Use when demonstrating or testing the plugin system's in-place skill discovery.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | hello-world |
| description | Minimal reference skill bundled with the hello-plugin example. Use when demonstrating or testing the plugin system's in-place skill discovery. |
This is a trivial skill bundled inside the hello-plugin example plugin
(crates/infra/bamboo-plugin/examples/hello-plugin/). It exists purely to
exercise the plugin system's schema end-to-end:
plugin.json declares it under provides.skills as "hello-world".~/.bamboo/plugins/hello-plugin/, this
skill is discovered in place — no copy, no symlink — because
~/.bamboo/plugins/hello-plugin/skills becomes an additional skill
discovery directory (see bamboo-skills' SkillDirectorySource::Plugin).When invoked, just greet the user and mention that you are the example skill
from the hello-plugin plugin.
Review code changes, pull requests, patches, or a scoped code area for actionable correctness, security, compatibility, and test risks with file and line evidence. Use for review or audit requests; do not use for general proofreading, feature implementation, or debugging a reported failure when the user wants a fix.
Diagnose a concrete failure, regression, crash, hang, flaky test, or incorrect runtime behavior by reproducing it, testing hypotheses, and identifying the evidence-backed root cause. Use when symptoms or failing output exist; do not use for feature implementation without a failure, general code review, or a conceptual explanation.
Build an executable implementation, migration, or rollout plan from read-only repository exploration, including constraints, dependencies, ordered changes, verification, risks, and rollback points. Use when the user asks for a plan or decomposition before implementation; do not use when they want a small change implemented now, a status summary, or a general explanation.
Investigate a technical or product question using current primary sources and relevant repository evidence, then synthesize cited facts, explicit inferences, uncertainties, and implications. Use when freshness, external documentation, comparisons, or multi-source evidence matter; do not use for simple stable facts, pure code implementation, or a review confined to an already provided patch.
Reduce unnecessary code complexity, duplication, indirection, or abstraction while preserving observable behavior and validating equivalence. Use for simplify, cleanup, or behavior-preserving refactor requests; do not use for adding features, diagnosing an unexplained failure, broad code review without a simplification goal, or cosmetic churn without a complexity benefit.
Use this skill whenever the user acts like Bamboo is their personal assistant. Triggers include stating commitments, deadlines, appointments, or recurring routines ("remind me to...", "I need to... by Friday", "every Monday I..."), asking to be reminded of something, agenda questions ("what's on my plate", "what's due today/this week", "what did I say I'd do"), morning or daily briefings, GTD-style triage of open items, breaking a big goal into steps, and marking things done or cancelled. Manages durable todos, events, reminders, and habits in the ledger so they survive across sessions and fire real reminders.