Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Temporal Cycle Detection

ASecurity

Identifies what recurring cycle a situation is an instance of and where in that cycle you currently are. Use when asked 'what cycle is this', 'where are we in the cycle', 'have we seen this before', 'detect the pattern', 'hype cycle', or 'where in the curve'.

19 stars
0 votes
0 copies
0 views
Added 9/19/2026
ai-agentsrust

Works with

cli

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill temporal-cycle-detection --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Temporal Cycle Detection?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Temporal Cycle Detection
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-temporal-cycle-detection/badge)](https://www.skillsdirectory.com/skills/rondoflow-temporal-cycle-detection)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: temporal-cycle-detection
description: "Identifies what recurring cycle a situation is an instance of and where in that cycle you currently are. Use when asked 'what cycle is this', 'where are we in the cycle', 'have we seen this before', 'detect the pattern', 'hype cycle', or 'where in the curve'."
---

# Temporal Cycle Detection

Every situation that feels unprecedented is usually an instance of a recurring cycle. Knowing your position in the cycle tells you what phase is coming, what actions are appropriate now versus premature, and which signals indicate divergence from the typical pattern — the most important signal of all. Acting as if a situation is unique when it is not forfeits the pattern's predictive value.

---

## Your Process

**Step 1: Describe Current State and Trajectory**
State what is happening now and how the situation has moved over the past period. Include: rate of change, sentiment, who is entering or exiting, resource flows, expectations.

**Framing check:** Confirm the specific situation before continuing. State what you've identified — the actual phenomenon or domain being analyzed and its key observable parameters — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the specific situation and what is changing]. Is that right?"
- **Header:** "Framing"
- **Options:**
  - **Yes — proceed** — framing is correct
  - **Adjust** — one element is off; user will correct it before you continue
  - **Reframe** — different situation than read; incorporate the correction before proceeding

**Step 2: Match to a Candidate Cycle**
Compare against the most common cycles:
- **Technology Hype Cycle (Gartner):** trigger → peak of inflated expectations → trough of disillusionment → slope of enlightenment → plateau of productivity
- **Product Adoption Curve (Rogers):** innovators → early adopters → early majority → late majority → laggards
- **Business/Economic Cycle:** expansion → peak → contraction → trough → recovery
- **Organisational Change Curve (Kübler-Ross adapted):** shock → denial → frustration → depression → experiment → decision → integration
- **Competitive Cycle:** emergence → growth → shakeout → maturity → decline/renewal
- **Market Cycle:** accumulation → markup → distribution → markdown

**Step 3: Map Current Position**
Place the situation on the curve. Be specific about which phase and where within the phase (early, mid, late).

**Step 4: Identify Phase Signs**
List the characteristic indicators of this phase. Which are present? Which are absent? Absent expected signs are as informative as present ones.

**Step 5: State the Typical Next Phase**
What normally follows this phase? What are the leading indicators that the transition has begun?

**Step 6: Note Divergences**
Where does this situation differ from the typical cycle? These divergences — not the pattern itself — are the most important signals. They indicate either a different cycle applies or this instance will unfold differently.

---

## Human Check-in

Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:

- **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?"
- **Header:** "Scope"
- **Options:**
  - **Full analysis** — Complete all steps, reasoning shown throughout
  - **Key findings only** — Bottom-line output, skip step-by-step detail
  - **Current position only** — Where in the cycle we are right now, skip the full cycle description
  - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing

Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.

## Output Format

**Cycle Match:** [cycle name] — [why it fits]

**Current Position:** [phase name] — [early / mid / late within phase]

**Phase Signs**

| Expected Sign for This Phase | Present? |
|------------------------------|---------|
| | |

**Typical Next Phase:** [name + leading indicators of transition]

**Divergences:** [where this instance differs from the typical pattern + what that implies]

**Implications:** [what actions are appropriate now vs. premature vs. overdue]

---

## Notes

If no cycle fits well, that is itself a finding — either the situation is genuinely novel or it requires a composite of two cycles. Name the mismatch explicitly rather than forcing a fit.

---

## What's Next

After delivering this output, use `AskUserQuestion` to offer the next move:

- **Question:** "Cycles detected. What's next?"
- **Header:** "Next"
- **Options:**
  - `/historical-cycle-detection` — Look for historical evidence that confirms the cycles
  - `/temporal-timing-analysis` — Time actions to the detected cycles
  - `/strategy-timing` — Align strategy with the cycle timing
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →