agent supply chain newsletter

AI Community

Skill notes

Step 1: Gather team members

Fetch the current list of agent-supply-chain team members from GitHub: Ask the user if any members should be excluded (e.g. people who moved teams).

Step 2: Read past newsletters for format reference

Search for the latest blog posts in the ASC1 Confluence space: mcp__claude_ai_Atlassian__searchConfluenceUsingCql with cql: type = "blogpost" AND space = "ASC1" ORDER BY created DESC (limit 3) Read the most recent newsletter with mcp__claude_ai_Atlassian__getConfluencePage (contentFormat: markdown, contentType: blog) to match its structure and tone. The newsletter format is: Header: greeting, team links (ASC1, ABLD, BARX, ADX spaces), OKR link, support channel link

Step 3: Research GitHub activity

For each team member, launch background agents (use run_in_background: true) to search merged PRs during the period. Split into batches of ~8 members per agent to parallelize. Each agent should run, for every user: Each agent should return a summary per user, grouped thematically (build improvements, CI/CD, new features, bug fixes, etc.). Skip trivial PRs (version bumps, dependency updates). Focus on items that impact teams outside Agent Supply Chain.

Step 4: Research Confluence activity

Launch a background agent to search for relevant documentation created during the period: With CQL queries: space = "ASC1" AND lastModified >= "START_DATE" AND lastModified <= "END_DATE" ORDER BY lastModified DESC (limit 25) space = "ADX" AND lastModified >= "START_DATE" AND lastModified <= "END_DATE" ORDER BY lastModified DESC (limit 25) Identify RFCs, design docs, operational reports, and guides that are newsletter-worthy.

Step 5: Synthesize and write the newsletter

Apply the newsletter guide's filter: "Is this information impacting a team outside of the Agent Supply Chain group?" Only include items where the answer is yes. For each item: Provide a quantifiable improvement (time saved, percentage change, cost reduction) when available Link to the relevant PR, Confluence page, or documentation Keep descriptions concise (2-4 sentences max per item)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@DataDog · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Gather team members

Fetch the current list of agent-supply-chain team members from GitHub: Ask the user if any members should be excluded (e.g. people who moved teams).

02
Step 2: Read past newsletters for format reference

Search for the latest blog posts in the ASC1 Confluence space: `mcp__claude_ai_Atlassian__searchConfluenceUsingCql` with `cql`: `type = "blogpost" AND space = "ASC1" ORDER BY created DESC` (limit 3) Read the most recent newsletter with `mcp__claude_ai_Atlassian__getConfluencePage` (contentFormat: `markdown`, contentType: `blog`) to match its structure and tone. The newsletter format is: Header: greeting, team links (ASC1, ABLD, BARX, ADX spaces), OKR link, support channel link

03
Step 3: Research GitHub activity

For each team member, launch background agents (use `run_in_background: true`) to search merged PRs during the period. Split into batches of ~8 members per agent to parallelize. Each agent should run, for every user: Each agent should return a summary per user, grouped thematically (build improvements, CI/CD, new features, bug fixes, etc.). Skip trivial PRs (version bumps, dependency updates). Focus on items that impact teams outside Agent Supply Chain.

04
Step 4: Research Confluence activity

Launch a background agent to search for relevant documentation created during the period: With CQL queries: `space = "ASC1" AND lastModified >= "START_DATE" AND lastModified <= "END_DATE" ORDER BY lastModified DESC` (limit 25) `space = "ADX" AND lastModified >= "START_DATE" AND lastModified <= "END_DATE" ORDER BY lastModified DESC` (limit 25) Identify RFCs, design docs, operational reports, and guides that are newsletter-worthy.

05
Step 5: Synthesize and write the newsletter

Apply the newsletter guide's filter: "Is this information impacting a team outside of the Agent Supply Chain group?" Only include items where the answer is yes. For each item: Provide a quantifiable improvement (time saved, percentage change, cost reduction) when available Link to the relevant PR, Confluence page, or documentation Keep descriptions concise (2-4 sentences max per item)

06
Step 6: Create outputs

Step 6: Create outputs

07
Step 7: Present results

Return to the user: Links to both the Confluence draft and Gmail draft A bullet-point summary of the sections covered Remind them to: Review both outputs for accuracy

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.