تشغيل أي مهارة في Manus بنقرة واحدة

temporal-expert

النجوم٠

التفرعات١٤

آخر تحديث٢٦ يونيو ٢٠٢٦ في ٠٤:٣٨

Use when adding scheduled, recurring, or AI workflow behavior to a Cogni node; deciding graph vs route vs own Temporal worker; working with /api/v1/schedules, GraphRunWorkflow, NodeTaskWorkflow, defineScheduledJob, or the shared scheduler-worker substrate.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

cogni-dao

cogni-dao/node-template

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	temporal-expert
description	Use when adding scheduled, recurring, or AI workflow behavior to a Cogni node; deciding graph vs route vs own Temporal worker; working with /api/v1/schedules, GraphRunWorkflow, NodeTaskWorkflow, defineScheduledJob, or the shared scheduler-worker substrate.

Temporal Expert

Read docs/guides/node-temporal.md first. It is the node-author guide.

Default stance:

Scheduled AI work is a graph run via GraphRunWorkflow.
Plain recurring work is a route, preferably declared with defineScheduledJob, via NodeTaskWorkflow.
Normal nodes do not add Temporal workflow code and do not run their own worker.
Per-node workers are a rare escape hatch for custom durable orchestration that the shared generic substrate cannot express.

When changing substrate design, also read:

docs/spec/substrate-temporal.md
docs/spec/temporal-patterns.md
docs/spec/langgraph-patterns.md

المزيد من هذا المستودع

نفس المستودع

node-styling

cogni-dao/node-template

Use whenever you customize a Cogni node's visual identity — branding, icon, name, theme colors, metadata, the public homepage, or chat suggestions. Triggers on "style this node", "rebrand", "customize the node", "make the homepage for <mission>", node launch/formation styling. The homepage is the main event, not an afterthought.

2026-06-190

dev-manager

cogni-dao/node-template

Orchestrate multiple dev agents (spawned subagents OR human-driven worktrees) against ONE story-level outcome — hold the e2e vision, decompose into non-overlapping linked tasks with freeze/secrets guardrails baked in, monitor the tasks for movement, and intervene only on collision or drift. Use when a problem is bigger than one PR and needs 2+ agents working linked tasks under a shared contract (node-template feature builds, substrate ports). Triggers: "manage these devs", "coordinate subagents", "split this into tasks for N agents", "hold the story while agents work the tasks", "dev manager".

2026-06-180

test-expert

cogni-dao/node-template

Authoritative reference for THIS node's test setup — the test layers it actually ships (unit, component, external, stack), the vitest configs, what runs in CI vs locally, testcontainers/RLS component setup, fake adapters + APP_ENV=test, and the non-obvious gotchas (dotenv CWD trap, skip-gate ordering, never-mock-the-DB). Use whenever writing a new test, deciding "which layer does this belong in", debugging a flaky test or a `.env.test`-not-loading error, running any `pnpm test:*`, working with testcontainers, touching fake adapters, or wondering whether a test runs in CI. This node is a single flat-layout app — not the operator monorepo.

2026-06-170

validate-candidate

cogni-dao/node-template

Close the deploy_verified loop for THIS node after a PR is flighted to its candidate deploy. Confirm the candidate build matches the PR head SHA via /version, enumerate impacted surfaces (API routes, UI pages, graphs), exercise each against the real deployed URL on both the human (Playwright) and agent (API) axes, query Loki for your own request when creds are available, then post an approve/fail scorecard as a PR comment. Use whenever the user says "validate the candidate deploy", "prove this PR on candidate", "close the deploy_verified loop", or runs "/validate-candidate" (with or without a PR number). NOT for pre-merge CI or local dev testing — this runs after the operator has flighted the PR.

2026-06-170

schema-update

cogni-dao/node-template

Use any time you are about to add, change, or migrate a Postgres or Doltgres table in this node — editing schema TS under `packages/db-schema/src` or `packages/doltgres-schema/src`, running `drizzle-kit generate`, writing a migration `.sql`, touching `meta/_journal.json` / `*_snapshot.json`, adding row-level security / tenant isolation (a table with a FK to `users` or `billing_accounts`), or debugging a migration that didn't apply on candidate. Mandatory before any schema edit. Covers the RLS-first rule + the component gate that enforces it.

2026-06-170

contribute-to-cogni

cogni-dao/node-template

Contribution loop for agents working in a Cogni node-template repo. Use when starting implementation, preparing a PR, or checking node/operator ownership boundaries.

2026-06-050

name	temporal-expert
description	Use when adding scheduled, recurring, or AI workflow behavior to a Cogni node; deciding graph vs route vs own Temporal worker; working with /api/v1/schedules, GraphRunWorkflow, NodeTaskWorkflow, defineScheduledJob, or the shared scheduler-worker substrate.

Temporal Expert

Read docs/guides/node-temporal.md first. It is the node-author guide.

Default stance:

Scheduled AI work is a graph run via GraphRunWorkflow.
Plain recurring work is a route, preferably declared with defineScheduledJob, via NodeTaskWorkflow.
Normal nodes do not add Temporal workflow code and do not run their own worker.
Per-node workers are a rare escape hatch for custom durable orchestration that the shared generic substrate cannot express.

When changing substrate design, also read:

docs/spec/substrate-temporal.md
docs/spec/temporal-patterns.md
docs/spec/langgraph-patterns.md