Skip to content

Add analyze-innersource-video Claude Code skill - #925

Draft
rrrutledge wants to merge 1 commit into
InnerSourceCommons:mainfrom
rrrutledge:add-analyze-innersource-video-skill
Draft

Add analyze-innersource-video Claude Code skill#925
rrrutledge wants to merge 1 commit into
InnerSourceCommons:mainfrom
rrrutledge:add-analyze-innersource-video-skill

Conversation

@rrrutledge

Copy link
Copy Markdown
Contributor

Summary

Checks in a Claude Code skill (.claude/skills/analyze-innersource-video/SKILL.md) that's been living only on one contributor's machine until now, despite already being used to produce a real merged PR (#909, Thales Group Known Instance).

The skill takes a YouTube URL of an InnerSource Commons talk and:

  • Fetches the transcript and video metadata (title, uploader, description - often the only source for the speaker's organization)
  • Surveys this repo's existing pattern patlets for thematically adjacent patterns
  • Categorizes the talk's content into Known Instance candidates, clarifications to an existing pattern, or new pattern candidates
  • Applies a "uniquely InnerSource" filter to screen out generic engineering advice that happens to come up in an InnerSource talk but isn't specific to cross-team/cross-org contribution dynamics
  • Always proposes and asks for confirmation before editing any file or opening a PR

Test plan

  • Confirm the skill loads correctly for Claude Code sessions working in this repo
  • Re-run the skill against a new talk and confirm the output format matches what's documented

🤖 Generated with Claude Code

Adds a Claude Code skill that analyzes an InnerSource Commons community
call video against this repo's pattern library: it fetches the talk's
transcript and metadata, surveys adjacent patterns, and categorizes the
talk's content into Known Instance candidates, clarifications to an
existing pattern, or genuinely new pattern candidates - applying a
"uniquely InnerSource" filter to screen out generic engineering advice
that isn't specific to cross-team, cross-org contribution dynamics.

The skill always proposes and asks for confirmation before editing any
pattern file or opening a PR - it never auto-commits. This was already
used manually to produce the Thales Group Known Instance PR (InnerSourceCommons#909); this
commit is the first time the skill itself is checked into the repo
rather than living only on one contributor's machine.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

### Step 3 — Survey adjacent patterns

Extract every pattern's title + patlet via a small script (write to `.tmp/extract_patlets.py`). Read the resulting file in full — you want the patlet, not just the title, to judge relevance.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All patterns (title + patlet) should be available in https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/README.md#list-of-patterns

Not sure if pointing Claude to this directly would make things easier/faster/cheaper?

(I haven't used Claude myself)

@spier spier added the ⚙️ Type - Meta Improving how we collaborate in this repo is the main focus of this issue / PR label Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

⚙️ Type - Meta Improving how we collaborate in this repo is the main focus of this issue / PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants