chain-system

Included with Lifetime

$97 forever

Create, list, and load multi-session chain links that capture work context for later continuation. Use when you want to save current progress, resume a project from a prior session, or inspect chain history. Triggers: chain link, chain load, chain list, save context, resume work, continue later, session handoff.

General

What this skill does


# Chain System

## Overview

Capture durable, structured summaries of work so a later session can resume without re-discovery. Provide three subcommands under one skill: `link`, `load`, and `list`.

## Usage

Invoke with a subcommand:

```text
$chain-system link <chain-name>
$chain-system load <chain-name>
$chain-system list
```

If the chain name is missing for `link` or `load`, ask the user for it.

## Chain Root

Default to `.claude/chains` to remain compatible with the existing Claude chain-system plugin. If the user explicitly wants Codex-only storage, switch to `.codex/chains` and confirm.

## Subcommands

### `link`

Create a new chain link summarizing the current work.

Steps:
1. Build a concise but complete summary using this structure:
   - Primary Request and Intent
   - Key Technical Concepts
   - Work Completed
   - Decisions and Rationale
   - Files and Code Changes (Created/Modified/Read)
   - Unresolved Issues and Blockers (only if any)
   - Pending Tasks
   - Current Work
   - Next Step
2. Create a slug (kebab-case) and a human readable title.
3. Create the directory: `mkdir -p .claude/chains/<chain-name>`.
4. Generate timestamp in local time: `date '+%Y-%m-%d-%H%M'`.
5. Write the summary to:
   `.claude/chains/<chain-name>/<timestamp>-<slug>.md`
6. Write only the summary (no analysis), then tell the user the file path and how to load it.

Use the same file format each time so `load` can extract summary and next step reliably.

### `load`

Load the most recent chain link for a named chain.

Steps:
1. Find the most recent link:
   - `ls .claude/chains/<chain-name>/*.md 2>/dev/null | sort -r | head -1`
2. If none, tell the user the chain does not exist and suggest `list`.
3. Read the file fully and internalize it as working context.
4. List the 5 most recent links:
   - `ls .claude/chains/<chain-name>/*.md 2>/dev/null | sort -r | head -5`
5. Detect insufficiency and ask questions if needed:
   - Missing context referenced by the link
   - Ambiguous "Next Step"
   - Stale link (>7 days old)
6. Show the user: chain name, most recent link filename, short summary, next step, and the 5 most recent links.
7. If any insufficiency flags exist, stop and clarify before proceeding.

### `list`

List all chains with counts and most recent link.

Steps:
1. Check for chains:
   - `ls -d .claude/chains/*/ 2>/dev/null`
2. For each chain, show:
   - chain name (directory)
   - link count (`ls .claude/chains/<chain-name>/*.md 2>/dev/null | wc -l`)
   - most recent link filename (`ls .claude/chains/<chain-name>/*.md 2>/dev/null | sort -r | head -1`)
3. If no chains exist, suggest `link` to start one.

Files: 6

Size: 10.5 KB

Complexity: 22/100

Category: General

Source: https://github.com/deevsdeevs/agent-system/tree/main/chain-system

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts