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 件のリポジトリを表示
すべてのリポジトリを表示しました