Skip to content
cccskills
FreePublished on GitHub

loop

Create and manage simple heartbeat automations attached to the current Codex thread. Use when Jason invokes $loop or asks this thread to keep going, check again, follow up, retry, monitor, or resume on a recurring cadence.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573 stars(GitHub 573 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Loop

Turn a plain-English request into a heartbeat on the current thread with as little ceremony as possible.

Set Up The Loop

  1. Infer the task from the request and current thread. Infer the stop condition when one is clear.
  2. Decide whether a heartbeat is useful. Use one when the work benefits from returning to this thread after time passes or external state may change; continue immediately instead when the task can simply be finished now.
  3. Use the requested cadence when sensible. Otherwise choose a cadence from the task's expected feedback latency, urgency, cost, and risk of noisy empty runs. Do not poll faster than the underlying state can plausibly change.
  4. Choose a short verb-led name and a self-contained task prompt. Put the work, its completion condition, and this terminal behavior in the prompt:
    • when the completion condition is met, rename the current thread to done: <short task name> using the thread-title tool without inventing a thread ID;
    • report the completed result and stop the loop. Keep timing and thread-target details in the automation fields.
  5. Call the automation tool with:
    • mode=create
    • kind=heartbeat
    • destination=thread
    • status=ACTIVE
    • the inferred name, prompt, and rrule
  6. After creation succeeds, rename the current thread to loop: <short task name> using the thread-title tool without inventing a thread ID.
  7. Return only the loop name, cadence, and what it will do.

Do not create a new thread, invent a thread ID, or substitute a detached cron job. Do not expose raw RRULE syntax to Jason.

Use Judgment

  • Ask when the task, cadence, stop condition, deadline, or notification behavior is materially ambiguous. Prefer the built-in user-question tool when it is available; otherwise ask one concise direct question.
  • When asking about cadence, offer a small set of task-appropriate choices and recommend one. Do not make Jason translate the task into scheduling jargon.
  • If the ambiguity is minor, make a reasonable assumption and state it instead of interrupting setup.
  • Treat “loop,” “keep going,” and “check again” as authorization to create the heartbeat requested in that message.
  • Preserve explicit deadlines, notification requirements, and stop conditions.
  • Keep the lifecycle prefixes exact: loop: while active and done: after successful completion.
  • Rename to done: only after successful completion, not after a failed run, pause, or temporary retry.
  • Prefer updating an existing matching automation over creating a duplicate.
  • For inspect, pause, resume, change, or delete requests, resolve the existing automation and use the corresponding automation-tool mode while preserving fields the user did not change. Restore the loop: title when resuming.
  • If the automation tool is unavailable, say so plainly. Never emit a raw automation directive as a workaround.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

assistant

Free

Meet or work with Assistant, the user's relaxed ongoing work support. Use when the user invokes Assistant, starts or resumes an Assistant chat, asks what they should know, wants proactive work awareness, asks for reply drafts, asks to keep an eye on work, or needs follow-up/check-in help. On first contact, start with exactly "Hi, I'm your assistant." then decide whether onboarding is brand new, partial, or already established.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

audit-ai-code

Free

Audit, de-slop, parameterize, modularize, or safely clean up AI-generated or AI-shaped backend/general code. Use for Python, TypeScript, or other implementation diffs that may contain duplicate helpers, fixture hacks, hard-coded test data, over-defensive control flow, broad exception wrappers, config-bag or boolean-mode soup, speculative scaffolding, hallucinated APIs/dependencies, local-idiom drift, brittle tests, or maintainability/safety/performance gaps after a feature, bugfix, prototype, or agent pass.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

audit-ai-frontend

Free

Audit AI-generated, AI-shaped, or AI-looking frontend code, UI screenshots, and design diffs. Use for prompts like "audit AI frontend", "de-slop UI", "componentize this screen", "parameterize this React/Tailwind/shadcn UI", "make it responsive/accessible", or "review design-system drift"; check component APIs, reusable props/data models, modular composition, shared primitives/tokens, responsive resilience, accessibility, copy quality, hard-coded fixture screens, one-off CSS piles, and generic cards/gradients/fonts.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

audit-ai-writing

Free

Audit pasted chatbot output, AI-cleanup diffs, wiki drafts, Markdown/MDX/docs, and source-backed articles for generic AI fluff, LLM writing tells, weak audience model, lack of theory of mind, inflated significance, vague attribution, leaked tokens, placeholders, broken markup, fabricated or mismatched citations, and detector false positives. Use for requests like "AI writing audit", "check for AI slop", "find writing fluff", "does this sound like ChatGPT", "cleanup LLM tells", "make this less generic", "verify these citations", "detector flagged this", or text containing turn0search0, oaicite, oai_citation, contentReference, utm_source=chatgpt.com, malformed references, or wrong target-format markup.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

gh-address-comments

Free

Help address review/issue comments on the open GitHub PR for the current branch using `oai_gh` or `gh`; verify auth first and prompt the user to authenticate if not logged in.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

gh-commit

Free

Review git changes and split them into semantic commits with clear messages. Use when the user asks to commit work, clean up local history, or group a mixed diff into logical commits. Do not commit on main or master unless the user explicitly asks.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

See all skills by jxnl

Report a problem with this skill