agentleFS
choiyounggichoiyounggi/auto-velog/skills/flush/SKILL.md

flush

Skill1 starsChanged 45 days agoMITView on GitHub

밀린 블로그 글감·초안 일괄 처리. 큐의 pending 글감과 drafts의 pending/deferred/blocked 초안을 목록으로 보여주고 사용자와 함께 처리. 여러 세션의 글감을 한 편으로 묶는 옵션 포함. "블로그 밀린 거 처리", "blog flush", "글감 정리" 등에 트리거.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. armenr/modelmux★ 2same name
    2. ogham-mcp/ogham-superpowers-bridge★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

Files
SKILL.md

auto-velog flush (수동 일괄 처리)

대화형 스킬이다 — headless 자동 실행용이 아니다.

1. 현황 파악

  • ~/.auto-velog/queue/*.jsonl의 pending row (.processed.jsonl 제외)
  • ~/.auto-velog/drafts/*.md의 frontmatter status가 pending / deferred / blocked / failed인 것

표로 보여준다: 글감 topic·angle·수확일 | 초안 제목·score·status.

2. 사용자와 처리 방향 결정

항목별로 선택지를 제시한다:

  • 초안 작성 — pending 글감을 draft 스킬 절차(심사→분석→집필→스캔)로 처리
  • 묶어서 한 편 — 주제가 이어지는 여러 글감을 하나의 글로 합친다 (예: 같은 프로젝트의 연속 삽질기). 합칠 후보를 먼저 제안할 것
  • 발행 — pending/deferred 초안을 publish 스킬 절차로 발행
  • blocked 해소 — 시크릿 스캔에 걸린 부분을 보여주고 함께 레드액션 후 재스캔
  • 버리기 — 글감/초안을 .processed.jsonl(status: dropped)로 이동

3. 마무리

처리 결과 요약(발행 URL, 남은 항목)을 보고하고 ~/.auto-velog/log.jsonl에 기록한다.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.