projectx: Skill for Claude Code

.agents/skills/temporal/SKILL.md

temporal is a skill for Claude Code from proyecto26/projectx. It costs 161 tokens per session (2,187 once invoked), scanned A, original, MIT.

A development guide for Temporal, a platform that runs workflows reliably even when services fail or restart.

In plain words
What is it for?
Use it to create or debug workflows and activities, handle retries, signals, queries, timeouts, worker problems, and workflow replay.
Why use it?
It explains how workflow history, task queues, workers, and time limits fit together, helping diagnose failures and nondeterministic behavior.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is proyecto26/projectx's own configuration. It tells Claude Code how to work on projectx itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything projectx configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import type * as activities from '../activities';.

Reuse

Borrowing it

Nothing to install: this file belongs to proyecto26/projectx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/proyecto26/projectx/develop/.agents/skills/temporal/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/proyecto26/projectx

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for temporal

README.md
[![agentmods](https://agentmods.dev/badge/skills/proyecto26/projectx/temporal/github.svg)](https://agentmods.dev/skills/proyecto26/projectx/temporal)
Your own site
<a href="https://agentmods.dev/skills/proyecto26/projectx/temporal"><img src="https://agentmods.dev/badge/skills/proyecto26/projectx/temporal/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for temporal

Your own site · 80×15
<a href="https://agentmods.dev/skills/proyecto26/projectx/temporal"><img src="https://agentmods.dev/badge/skills/proyecto26/projectx/temporal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 161 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,187 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00161 $0.02187
Opus 5.5 $0.00064 $0.00875
Sonnet 5.5 $0.00032 $0.00437
Haiku 4.5 $0.00016 $0.00219

Measured 2mo ago against content hash b703751f146e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

temporal scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/temporal/SKILL.md · 251 lines

How it starts

The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Temporal Workflow Development

Overview

Temporal is a durable execution platform that makes workflows survive failures automatically. This skill provides guidance for building Temporal applications.

Core Architecture

The Temporal Cluster is the central orchestration backend. It maintains three key subsystems: the Event History (a durable log of all workflow state), Task Queues (which route work to the right workers), and a Visibility store (for searching and listing workflows). There are three ways to run a Cluster:

  • Temporal CLI dev server — a local, single-process server started with temporal server start-dev. Suitable for development and testing only, not production.
  • Self-hosted — you deploy and manage the Temporal server and its dependencies (e.g., database) in your own infrastructure for production use.
  • Temporal Cloud — a fully managed production service operated by Temporal. No cluster infrastructure to manage.

Workers are long-running processes that you run and manage. They poll Task Queues for work and execute your code. You might run a single Worker process on one machine during development, or run many Worker processes across a large fleet of machines in production. Each Worker hosts two types of code:

  • Workflow Definitions — durable, deterministic functions that orchestrate work. These must not have side effects.
  • Activity Implementations — non-deterministic operations (API calls, file I/O, etc.) that can fail and be retried.

Workers communicate with the Cluster via a poll/complete loop: they poll a Task Queue for tasks, execute the corresponding Workflow or Activity code, and report results back.

History Replay: Why Determinism Matters

Temporal achieves durability through history replay:

  1. Initial Execution - Worker runs workflow, generates Commands, stored as Events in history
  2. Recovery - On restart/failure, Worker re-executes workflow from beginning
  3. Matching - SDK compares generated Commands against stored Events
  4. Restoration - Uses stored Activity results instead of re-executing

Read the full file on GitHub · 251 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 251 lines · 161 tokens per session scan A b703751f146e

Subscribe to this mod's changes

temporal is a skill published in the GitHub repository proyecto26/projectx (83 stars, last pushed yesterday), licensed MIT. It adds 161 tokens to every session and 2,187 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

temporal compared with skills from other repositories

temporal next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
temporalproyecto26/projectxSkill83yesterdayMITA161Claude Code
scaffold-projectMarve10s/Better-FullstackSkill818yesterdayMITA80Claude Code
evjsafx-team/evjsSkill274d agoMITA45Claude Code, Codex
nextjs-expertpersonamanagmentlayer/pclSkill4411d agoApache-2.0A77Claude Code
remix-expertpersonamanagmentlayer/pclSkill4411d agoApache-2.0A70Claude Code
nifra-apinifrajs/nifraSkill6todayMITA73Claude Code
nifra-webnifrajs/nifraSkill6todayMITA85Claude Code