本文へ移動
cccskills
無料GitHub で公開

sync-skills

Fetch skills from projects on the current system, genericize them, and add to the claude-skills repository. Use when user says "sync skills", "fetch skills", "import skills from projects", or wants to pull skills from their local projects into this public repo.

qa-aman/claude-skills
インストール方法を見る

含まれるファイル（1）

  • SKILL.md5.7 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Sync Skills from Local Projects

Overview

This skill scans projects on the current system for Claude Code skills (.claude/skills/ directories), identifies new or updated skills, genericizes them by stripping project-specific content, and adds them to this repository.

Workflow

Step 1: Identify the Claude Skills Repo

The target repo is the claude-skills project. Confirm its location - it should be the current working directory or specified by the user.

Step 2: Scan for Skills

Search for skills across local projects:

Find all directories matching: <projects-root>/*/.claude/skills/*/SKILL.md

Default projects root: [your projects root] (e.g. ~/Documents/Projects/). The user may override this with a different path.

For each found skill, collect:

  • Skill name (directory name)
  • Source project name
  • SKILL.md content
  • Any files in references/, assets/, scripts/ subdirectories

Step 3: Deduplicate

Compare found skills against skills already in skills/by-role/ and skills/shared/ directories of this repo:

  • New skill: not present in repo - proceed to genericize
  • Updated skill: present but source has newer/different content - show diff, ask user whether to update
  • Identical: skip silently

Step 4: Determine the Role

For each new skill, determine which role folder it belongs in:

Valid roles: pm, engineer, qa, designer, content-creator, devops, shared, leadership, program-delivery-manager, customer-success, recruiter, consultant, sales, marketing, founder, data-scientist, data-engineer, security

If the role is unclear, ask the user before proceeding.

Step 5: Genericize

For each new or updated skill, apply these transformations:

Replace personal references:

  • Author names, handles, usernames -> remove or replace with [your name]
  • Newsletter/blog names -> [your newsletter]
  • Specific domains (e.g., name.substack.com) -> [your-domain]
  • Niche or topic tied to the author -> [your niche] or [your topic]
  • Company names -> [your company]
  • Team names -> [your team]
  • Client names -> [your client]
  • Project-specific program names -> [your program]

Remove project-specific content:

  • File paths referencing the source project
  • References to other project-specific skills, configs, or workflows
  • Environment variables specific to the source project
  • API keys, tokens, or credentials (should never exist, but check)

Preserve:

  • The skill's core logic, frameworks, and checklists
  • Generic examples and templates
  • Anti-patterns and quality criteria
  • References to general tools or platforms (LinkedIn, Substack, etc.)
  • The book or methodology the skill is grounded in

Verify:

  • YAML frontmatter has name and description fields
  • Description has multiple trigger phrases and is pushy
  • Body is under 500 lines
  • No personal/project-specific content remains
  • Skill is self-contained (no broken references to removed content)

Step 6: Add to Repo

For each genericized skill, use init_skill.py to scaffold and register in skills.json:

python3 scripts/init_skill.py <skill-name> --role <role> --description "<one-liner>" --tags "<tag1,tag2>"

This creates skills/by-role/<role>/<skill-name>/SKILL.md and adds the entry to skills.json automatically.

Then overwrite the scaffolded SKILL.md with the genericized content.

Do not manually edit install.sh - it reads from skills.json. The registry is the source of truth.

Step 7: Validate

python3 scripts/validate_skill.py

All skills must pass before committing.

Step 8: Update README

Add a row to the correct role table in README.md:

| `skill-name` | What it does | Book/methodology source |

Step 9: Report and Commit

Output a summary:

  • Skills added (with source project and role assigned)
  • Skills updated (with what changed)
  • Skills skipped (already identical)
  • Skills needing manual review (couldn't fully genericize)

Commit with a clear message:

git add skills/by-role/<role>/<skill-name>/ skills.json README.md
git commit -m "sync <skill-name> from [source project]"

Anti-Patterns

Don't blindly copy. Always read the source skill first. Some skills are deeply project-specific and can't be genericized.

Don't merge skills. If two projects have different versions of the same skill, ask the user which to keep.

Don't strip too much. The goal is to remove personal references, not gut the content. Frameworks, examples, and checklists should survive intact.

Don't forget supporting files. Check for references/, assets/, scripts/ subdirectories and copy them too.

Don't edit install.sh directly. Use init_skill.py to register skills. install.sh reads from skills.json - the hardcoded array no longer exists.

Quality Checklist

Before completing sync:

  • Each new skill scaffolded with init_skill.py (creates folder + registers in skills.json)
  • Each new skill has valid YAML frontmatter (name + description)
  • Description has multiple trigger phrases
  • No personal names, domains, or project paths remain
  • Placeholder brackets used consistently: [your niche], [your newsletter], [your-domain], [your name], [your company], [your team], [your client]
  • README.md skills table updated with new row
  • python3 scripts/validate_skill.py passes
  • Each skill is self-contained and works standalone
  • Body under 500 lines per SKILL.md

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

11-star-framework

無料

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年10月13日 更新

ab-copy-writer

無料

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年10月13日 更新

acceptance-criteria-writer

無料

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年10月13日 更新

account-plan

無料

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年10月13日 更新

ad-campaign-writer

無料

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年10月13日 更新

api-design

無料

Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年10月13日 更新

qa-aman のスキルをすべて見る

このスキルの問題を報告する