본문으로 건너뛰기
cccskills
무료GitHub에 공개

index-refresh

Refresh an LLM Wiki index against the pages that actually exist. Add missing entries, remove entries for deleted pages, preserve custom categories, and log change counts while leaving page bodies untouched.

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

원문원문 설명 보기

Use when an LLM Wiki operation issue requests an index refresh. Rebuild `wiki/index.md` from the actual wiki tree, reconcile missing/deleted entries, and log counts without editing page bodies.

설치 방법 보기

이럴 때 유용합니다

  • Add existing pages missing from the wiki index
  • Remove index entries for deleted pages
  • Organize project entries and related standup links
  • Record index refresh results and change counts

포함된 파일(1)

  • SKILL.md3.9 KB

SKILL.md(원문)

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

Index Refresh

Keep wiki/index.md accurate and scannable. The index is the maintainer's first stop for navigation — its quality determines how cheap every subsequent operation becomes.

Inputs

  • An operation issue with operationType: "index" (or the index-refresh routine title).
  • The operation issue's target wikiId, spaceSlug, and space root. Refresh only that space unless the issue explicitly says this is a multi-space sweep.

Workflow

  1. Read the target space's wiki/index.md as it currently stands.
  2. Walk the target space's wiki/. wiki/projects/<slug>/standup.md entries are current-state companions for durable wiki/projects/<slug>/index.md pages; index them only as links attached to the matching project entry. Walk wiki/ by category (sources/, projects/, entities/, concepts/, synthesis/, plus any custom subdirectories the wiki schema added).
  3. Read the target space's last ~50 entries of wiki/log.md to spot pages that were created or substantially changed but never made it to the index.
  4. Per category, produce sorted entries of the form:
    - [[<path>]] — <one-line summary>
    
    The summary is one factual sentence pulled from the page's first paragraph or its title. No status, no datestamps in the index — those belong in the page itself or in the log.
  5. Drop entries whose page no longer exists. Note the deletion in the log:
    ## [YYYY-MM-DD] index-refresh | reconciled
    - removed: [[wiki/old-page]] (page deleted)
    - added: [[wiki/new-page]] — <summary>
    
  6. Add entries for pages that exist on disk but were missing from the index. Skip wiki/log.md and wiki/index.md themselves. For standalone wiki/projects/<slug>/standup.md without a matching durable project page, add it under Projects and flag it for later durable-page distillation.
  7. Write project entries editorially. The Projects section should group work by the project's concept and purpose, not by issue ids, dates, statuses, UUIDs, or source metadata. Link task identifiers only as supporting evidence.
  8. Preserve custom categories. If the wiki has added e.g. wiki/papers/ or wiki/runbooks/, keep its index section. Do not collapse to the default five categories.
  9. Append a log entry with counts:
    ## [YYYY-MM-DD] index-refresh | added=N removed=M
    - operation issue: <issue identifier>
    
    If the index was already accurate, the log entry says added=0 removed=0 — still write it so future audits can see the run happened.

What this skill does NOT do

  • Does not change page content.
  • Does not resolve contradictions, fix broken links, or fill concept gaps. Those go to the next wiki-lint run.
  • Does not write summaries that are not already supported by the page itself. If a page lacks a clear first paragraph to summarise, flag it for wiki-lint.

Voice

  • Index entries are one factual line per page, present tense.
  • No emojis, no statuses, no dates in wiki/index.md. Dates live in the log.

Verification

Before closing the operation issue:

  • wiki/index.md matches the actual contents of wiki/ — no missing pages, no dangling entries.
  • Project entries include current wiki/projects/<slug>/standup.md links when standups exist.
  • Each index line has the form - [[path]] — <summary>.
  • Custom category sections are preserved.
  • wiki/log.md has the index-refresh entry with counts (even if the counts are zero).
  • No page bodies were modified. No file under raw/ was modified.

Tools

wiki_search, wiki_read_page, wiki_write_page (for wiki/index.md and wiki/log.md only). Always include the operation issue's wikiId and spaceSlug.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Add or extend Paperclip end-to-end evaluations that exercise real browser workflows across the server, database, and runner. Define expected outcomes, check independent evidence, and connect results to the existing reporting pipeline for local or Daytona execution.

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

  • Adding an evaluation for a complete user workflow
  • Updating test data and outcome checks
  • Including screenshots and artifacts in evaluation reports
paperclipai/paperclip10.4만2026년 10월 18일 업데이트

Add or extend Paperclip Runner evaluations that test real sessions against a mock control service. Define observable pass conditions, validate cases and run selections, and retain source revisions, evidence, and costs for authorized live runs.

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

  • Adding a focused Runner protocol evaluation
  • Testing grading rules with valid and invalid evidence
  • Updating evaluation selections and campaign membership
paperclipai/paperclip10.4만2026년 10월 18일 업데이트

Use a real browser to verify web pages and apps through short, supervised interactions. Capture screenshots, inspect errors and network requests, and document reproducible steps for UI bugs or expected behavior checks.

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

  • Capture screenshots to verify UI changes
  • Read content rendered by JavaScript
  • Reproduce UI bugs and record errors
paperclipai/paperclip10.4만2026년 10월 18일 업데이트

agentmail

무료

Read email linked to assigned Paperclip tasks, send new messages or replies through an assigned AgentMail inbox, and check delivery outcomes. Follow task permissions and preserve retry identifiers to avoid duplicate sends.

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

  • Reading email context attached to an assigned task
  • Sending a new email from an assigned inbox
  • Replying to a specific message in a conversation
paperclipai/paperclip10.4만2026년 10월 18일 업데이트

check-pr

무료

Inspect proposed changes in GitHub, GitLab, or Perforce for review feedback, failed automated checks, and incomplete descriptions. It separates actionable findings from informational or resolved comments, then helps fix issues and close addressed review threads when requested.

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

  • Inspect a change before submission
  • Identify failed checks and required fixes
  • Organize human and bot review feedback
paperclipai/paperclip10.4만2026년 10월 18일 업데이트

Create an AI agent company or team package from an idea or an existing repository. Define roles, reporting lines, skills, and work handoffs, then generate structured files that follow the Agent Companies specification.

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

  • Build an agent company from an idea
  • Turn a repository into an agent team package
  • Define agent roles and work handoffs
paperclipai/paperclip10.4만2026년 10월 18일 업데이트

paperclipai의 스킬 모두 보기

이 스킬의 문제 신고