Skip to main content
Manus에서 모든 스킬 실행
원클릭으로
getkyo
GitHub 제작자 프로필

getkyo

1개 GitHub 저장소에서 수집된 7개 skills를 저장소 단위로 보여줍니다.

수집된 skills
7
저장소
1
업데이트
2026-06-12
저장소 지도

skills가 있는 위치

수집된 skill 수가 많은 주요 저장소와 이 제작자 카탈로그 내 비중, 직업 분포를 보여줍니다.

저장소 탐색

저장소와 대표 skills

readme-verify
소프트웨어 개발자

Three-gate verification for a finalized README: companion script structural check, chunk-by-chunk forward-reference walk, and skim-reader persona walkthrough with a line-grounded spine test.

2026-06-12
readme
소프트웨어 개발자

Write or review a high-quality README that serves engaged readers, not audit checklists. Cuts bloat by default; only adds when the addition closes a question the reader is actually asking.

2026-06-02
readme-analyze-existing
소프트웨어 개발자

Diagnose an existing README against the source-analysis output and produce a structured action list (CUT/RELOCATE/RESTRUCTURE/REWRITE-HEADING/REORDER/ADD-CALLOUT) consumed by readme-edit. Splits its work into 0(a)(i) source-only draft, 0(a)(ii) anchored diagnosis.

2026-05-29
readme-analyze-source
소프트웨어 개발자

Analyze a module's source code to produce a spine candidate, callout list, and API surface inventory for use by readme-draft and readme-analyze-existing.

2026-05-29
readme-critique
소프트웨어 개발자

High-judgment whole-document review for shape, pedagogy, and design-rationale. Catches the catalog-vs-teaching, composition-vs-enumeration, running-domain-vs-ad-hoc failure modes that readme-verify's gates pass on. Runs between draft and verify.

2026-05-29
readme-draft
소프트웨어 개발자

Draft a README from a source-analysis output (spine + callouts + API inventory). For new READMEs or full rewrites. Length scales with API surface; never invents content not in the inventory.

2026-05-29
readme-edit
소프트웨어 개발자

Apply a structured action list (CUT/RELOCATE/RESTRUCTURE/REWRITE-HEADING/REORDER/ADD-CALLOUT) to a README. Mechanical only; no diagnosis. Em-dash removal must rewrite the sentence, not substitute punctuation.

2026-05-29
저장소 1개 중 1개 표시
모든 저장소를 표시했습니다