본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template스타 573(GitHub 573 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

assistant

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

audit-ai-code

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

audit-ai-frontend

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

audit-ai-writing

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

gh-address-comments

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

gh-commit

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

jxnl의 스킬 모두 보기

이 스킬의 문제 신고