gas-dev
Skill0 starsChanged 3 months agoNo licenceView on GitHub
GAS(Google Apps Script)開発を一気通貫で回すオーケストレータースキル。①gas-clone(スクリプトIDの特定とローカルへのクローン)→ ②business-understanding(業務整理)→ ③dev-docs init(要件定義・永続ドキュメント整備)→ ④add-feature(機能開発)→ ⑤gas-push(clasp status 確認とリモート反映)の5フェーズを、プロジェクトの状態を検出して途中からでも正しい順に進める。「GAS開発を始めたい」「この案件のGAS改修を最初から最後まで」「GAS開発フローで進めて」「クローンからpushまで一通り」「いつものGASの流れで」など、GAS開発の工程全体・複数フェーズにまたがる依頼が来たら必ずこのスキルを使うこと。単発の作業には各スキルを直接使う(クローンだけ→gas-clone、pushだけ→gas-push、機能追加だけ→add-feature、業務整理だけ→business-understanding)。
1 other project uses a version of this.
Adopted by
Most recently taken up by
- AiRaise/claude-skillstheir own version, first seen Jul 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- AiRaise/claude-skills★ 1same 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 repository14 other files it gives its agents.
- add-featureSkill
- atlas-pptx-designSkill
- atlas-registerSkill
- business-understandingSkill
- daily-reportSkill
- decision-rulesSkill
- dev-docsSkill
- drawio-shotsSkill
- gas-cloneSkill
- gas-pushSkill
- hearing-sheetSkill
- natural-japaneseSkill
- obsidian-logSkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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
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.

