القائمة
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/agentculture/culture-nodes --skill sampleيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Comment on, create, and read Jira issues from the operator lane, using the Jira credential already granted to the sweep on thor (the credential never leaves that host — the script runs its API calls there over ssh). Verbs: `show <ISSUE>` reads summary, status and the last five comments with ids and author account ids; `comment <ISSUE> "<text>"` posts a comment and prints its id; `create --project KEY --summary "<text>" [--type Task] [--description "<text>"]` files an issue and prints its key. Everything it writes lands UNDER THE SYSTEM'S JIRA ACCOUNT, so the sweep filters those comments as self-echo by account id (`examples/pr-upkeep/pr_upkeep_jira.py` `jira_comment_is_self_echo`): this is the operator's own hand on the board — for creating proof tickets and reading what the sweep will see — NOT a way to produce a human's fact. The system's own board moves go through the jira bridge actor's allowlisted verbs, never through this. Use when the operator says "comment on SCRUM-5", "open a proof ticket", "what doe
Drive a running culture-nodes control plane: inspect runs/ledger/actors, author + validate + publish workflows, and assign real work to registered agent actors (codex-thor, codex-orin) through the normal engine dispatch path. Use when the user says "assign this to codex", "run it through nodes", "create a workflow for X", "what's running", "cancel that run", "check the ledger", or when you want to delegate a scoped task to the production actor fleet instead of doing it in-session. Works for ANY operator with the skill — Claude, the colleague backend, codex sessions, or a human at a shell — plain bash + curl + python3 against the public v1alpha1 HTTP API.
Fan out a converged devague plan's dependency waves to parallel agents in isolated git worktrees, one agent per task per wave, with TDD-gated merges by the main agent. Human gates: the exported spec, the implementation split plan (task map + per-task agent/model proposal + go/no-go), and the final PR. The devague CLI stays deterministic and non-orchestrating (#20) — it only *describes* the graph via `devague plan waves`; the operator (main agent) performs the fan-out. Use when the user says "assign to workforce", "fan out the plan", "parallel subagents", or after the `spec-to-plan` skill exports a plan. Authored and maintained in agentculture/devague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the other skills here.
عرض SKILL.md
| name | sample |
| description | Fixture skill proving the .qwen/skills leg carries at least one skill. |
