Add clickable repo links in weekly articles (#33)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Juan Manuel Servera committed
May 18, 2026 at 13:37 UTC
2d255382ed01f0de9a7d296c0d84bfbde1830273
5 files changed
+21
-12
.squad/agents/farnsworth/history.md
+1
@@ -18,3 +18,4 @@
18
- **2026-05-18T12:07:20.778+02:00:** The analyzer contract should be a superset of Amy's weekly page frontmatter plus Leela's `quality_score` gate, so one analyzed artifact can satisfy both editorial review and generator input.
19
- **2026-05-18T12:07:20.778+02:00:** The analyzer contract should be a superset of Amy’s weekly page frontmatter plus Leela’s `quality_score` gate, so one analyzed artifact can satisfy both editorial review and generator input.
20
- **2026-05-18T12:07:20.778+02:00:** Keep the reader-facing weekly summary in five stable H2 sections, but require labeled `Signal`, `Noise`, and `Gaps` subsections so the editorial lens remains explicit and machine-checkable.
21
+- **2026-05-18T13:20:07.067+02:00:** Weekly analysis prose should render repo mentions as explicit GitHub markdown links, and the current raw crawl artifact exposes those repo page URLs under `url` rather than `html_url`, so analyzer/generator prompts should require link formatting without assuming a different field name.
content/weekly/2026/W21.md
+2
-2
@@ -17,11 +17,11 @@ _Manual dry-run weekly page generated from `data/analyzed/2026-W21-summary.md` u
17
18
## Notable New Repos
19
20
-The clearest new-repo signal is a cluster of agent-focused developer tooling. **vercel-labs/zero** leads the week as a high-interest launch with a sharp positioning statement, while **DenisSergeevitch/agents-best-practices**, **Kappaemme-git/codex-complexity-optimizer**, **gi-dellav/zerostack**, and **openclaw/clawpatch** all reinforce the same theme: teams want lighter runtimes, safer automation, and reusable workflows for coding agents. Outside that lane, **facebookresearch/vggt-omega** provides a strong research signal in vision, and **chrisbanes/skills** suggests that packaged “skills” are becoming a recognizable way to ship knowledge for developer tools.
20
+The clearest new-repo signal is a cluster of agent-focused developer tooling. [vercel-labs/zero](https://github.com/vercel-labs/zero) leads the week as a high-interest launch with a sharp positioning statement, while [DenisSergeevitch/agents-best-practices](https://github.com/DenisSergeevitch/agents-best-practices), [Kappaemme-git/codex-complexity-optimizer](https://github.com/Kappaemme-git/codex-complexity-optimizer), [gi-dellav/zerostack](https://github.com/gi-dellav/zerostack), and [openclaw/clawpatch](https://github.com/openclaw/clawpatch) all reinforce the same theme: teams want lighter runtimes, safer automation, and reusable workflows for coding agents. Outside that lane, [facebookresearch/vggt-omega](https://github.com/facebookresearch/vggt-omega) provides a strong research signal in vision, and [chrisbanes/skills](https://github.com/chrisbanes/skills) suggests that packaged “skills” are becoming a recognizable way to ship knowledge for developer tools.
21
22
## Trending This Week
23
24
-The active heavyweight set includes **freeCodeCamp/freeCodeCamp**, **public-apis/public-apis**, **facebook/react**, **n8n-io/n8n**, **ollama/ollama**, **huggingface/transformers**, **langgenius/dify**, **firecrawl/firecrawl**, and **anthropics/claude-code**. That mix still points to real demand around AI workflow platforms, coding agents, and developer productivity infrastructure. The limitation is that this week has no historical star baseline, so the list behaves more like “widely watched repos touched this week” than a strict stars-gained leaderboard.
24
+The active heavyweight set includes [freeCodeCamp/freeCodeCamp](https://github.com/freeCodeCamp/freeCodeCamp), [public-apis/public-apis](https://github.com/public-apis/public-apis), [facebook/react](https://github.com/facebook/react), [n8n-io/n8n](https://github.com/n8n-io/n8n), [ollama/ollama](https://github.com/ollama/ollama), [huggingface/transformers](https://github.com/huggingface/transformers), [langgenius/dify](https://github.com/langgenius/dify), [firecrawl/firecrawl](https://github.com/firecrawl/firecrawl), and [anthropics/claude-code](https://github.com/anthropics/claude-code). That mix still points to real demand around AI workflow platforms, coding agents, and developer productivity infrastructure. The limitation is that this week has no historical star baseline, so the list behaves more like “widely watched repos touched this week” than a strict stars-gained leaderboard.
25
26
## Trend Analysis
27
data/analyzed/2026-W21-summary.md
+3
-3
@@ -14,13 +14,13 @@ summary: "Week 21 shows real demand for agent infrastructure, but the trend data
14
15
## Notable New Repositories
16
17
-The strongest new-repo signal is not raw volume but coherence. **vercel-labs/zero** anchors the week because it reads like a serious attempt to simplify agent-facing infrastructure rather than another thin wrapper. Around it, **DenisSergeevitch/agents-best-practices**, **Kappaemme-git/codex-complexity-optimizer**, **gi-dellav/zerostack**, and **openclaw/clawpatch** all point in the same direction: teams want safer automation, lighter execution layers, and better operating discipline for coding agents. That cluster matters more than any single launch because it suggests the market is already moving from “agents are interesting” to “agents need tooling that survives contact with real work.”
17
+The strongest new-repo signal is not raw volume but coherence. [vercel-labs/zero](https://github.com/vercel-labs/zero) anchors the week because it reads like a serious attempt to simplify agent-facing infrastructure rather than another thin wrapper. Around it, [DenisSergeevitch/agents-best-practices](https://github.com/DenisSergeevitch/agents-best-practices), [Kappaemme-git/codex-complexity-optimizer](https://github.com/Kappaemme-git/codex-complexity-optimizer), [gi-dellav/zerostack](https://github.com/gi-dellav/zerostack), and [openclaw/clawpatch](https://github.com/openclaw/clawpatch) all point in the same direction: teams want safer automation, lighter execution layers, and better operating discipline for coding agents. That cluster matters more than any single launch because it suggests the market is already moving from “agents are interesting” to “agents need tooling that survives contact with real work.”
18
19
-Outside that lane, **facebookresearch/vggt-omega** adds a more credible research signal than most of the week’s AI launches, and **chrisbanes/skills** hints that reusable skill packs may become a durable packaging pattern. The key takeaway is that the best new repos are the ones reducing workflow friction, not the ones making the loudest promises.
19
+Outside that lane, [facebookresearch/vggt-omega](https://github.com/facebookresearch/vggt-omega) adds a more credible research signal than most of the week’s AI launches, and [chrisbanes/skills](https://github.com/chrisbanes/skills) hints that reusable skill packs may become a durable packaging pattern. The key takeaway is that the best new repos are the ones reducing workflow friction, not the ones making the loudest promises.
20
21
## Trending This Week
22
23
-The trending set is still useful, but this week it is not a true stars-gained leaderboard. Every sampled `trending_repos` entry lacks a usable `stars_gained` value, so the list behaves more like “large repositories that were active during the crawl window” than a clean momentum table. Even with that caveat, the concentration around **freeCodeCamp/freeCodeCamp**, **facebook/react**, **n8n-io/n8n**, **ollama/ollama**, **huggingface/transformers**, **langgenius/dify**, **firecrawl/firecrawl**, and **anthropics/claude-code** shows that AI workflow platforms, developer productivity infrastructure, and agent-adjacent tooling remain where attention is pooling.
23
+The trending set is still useful, but this week it is not a true stars-gained leaderboard. Every sampled `trending_repos` entry lacks a usable `stars_gained` value, so the list behaves more like “large repositories that were active during the crawl window” than a clean momentum table. Even with that caveat, the concentration around [freeCodeCamp/freeCodeCamp](https://github.com/freeCodeCamp/freeCodeCamp), [facebook/react](https://github.com/facebook/react), [n8n-io/n8n](https://github.com/n8n-io/n8n), [ollama/ollama](https://github.com/ollama/ollama), [huggingface/transformers](https://github.com/huggingface/transformers), [langgenius/dify](https://github.com/langgenius/dify), [firecrawl/firecrawl](https://github.com/firecrawl/firecrawl), and [anthropics/claude-code](https://github.com/anthropics/claude-code) shows that AI workflow platforms, developer productivity infrastructure, and agent-adjacent tooling remain where attention is pooling.
24
25
## Trend Analysis
26
docs/analysis-spec.md
+7
@@ -227,11 +227,14 @@ The body must follow this exact top-level section order:
227
## Conclusion
228
```
229
230
+Every repository mentioned in the body must be rendered as a clickable markdown link in this exact format: `[owner/repo](https://github.com/owner/repo)`.
231
+
232
### Section guidance
233
234
#### 1. Notable New Repositories
235
- **Purpose:** Curate the week’s most credible new launches.
236
- **Include:** 3-7 repos, grouped into a coherent story rather than a bullet dump.
237
+- **Repo links:** Every repo mention must use `[owner/repo](https://github.com/owner/repo)`.
238
- **Tone:** Selective and judgmental.
239
- **Length:** ~120-220 words.
240
- **Avoid:** Exhaustive listings or copy/pasted repo descriptions.
@@ -239,6 +242,7 @@ The body must follow this exact top-level section order:
242
#### 2. Trending This Week
243
- **Purpose:** Explain where attention moved.
244
- **Include:** The most relevant momentum winners, plus a caveat if `stars_gained` is unavailable.
245
+- **Repo links:** Every repo mention must use `[owner/repo](https://github.com/owner/repo)`.
246
- **Tone:** Analytical, not celebratory.
247
- **Length:** ~100-180 words.
248
- **Avoid:** Treating raw popularity as momentum when deltas are missing.
@@ -248,6 +252,7 @@ The body must follow this exact top-level section order:
252
- **Required subsections:**
253
- `### Signal` — what looks durable or strategically important.
254
- `### Noise` — what looks inflated, repetitive, or low-substance.
255
+- **Repo links:** Every repo mention must use `[owner/repo](https://github.com/owner/repo)`.
256
- **Length:** ~150-260 words total.
257
- **Avoid:** Repeating section 1 and section 2 without synthesis.
258
@@ -255,12 +260,14 @@ The body must follow this exact top-level section order:
260
- **Purpose:** Surface absent or underweighted themes.
261
- **Required subsection:** `### Gaps`.
262
- **Include:** 2-4 concrete blind spots or underserved categories.
263
+- **Repo links:** Every repo mention must use `[owner/repo](https://github.com/owner/repo)`.
264
- **Length:** ~80-160 words.
265
- **Avoid:** Generic filler like “more innovation is needed.”
266
267
#### 5. Conclusion
268
- **Purpose:** End with a clear editorial takeaway.
269
- **Include:** Why the week matters and what to watch next.
270
+- **Repo links:** Every repo mention must use `[owner/repo](https://github.com/owner/repo)`.
271
- **Length:** ~50-110 words.
272
- **Avoid:** Introducing brand-new evidence.
273
prompts/analyze-weekly.md
+8
-7
@@ -97,7 +97,8 @@ Be critical, selective, and opinionated.
97
- `## Conclusion`: ~50-110 words focused on why the week matters and what to watch next.
98
15. The body must be at least 200 words.
99
16. Do not include raw JSON, notes to self, placeholders, or tool transcripts.
100
-17. Output only the finished markdown file content.
100
+17. Every repository reference in the body must be a clickable GitHub markdown link in this exact format: `[owner/repo](https://github.com/owner/repo)`.
101
+18. Output only the finished markdown file content.
102
103
## Working method
104
@@ -128,29 +129,29 @@ summary: "One-sentence editorial thesis."
129
130
## Notable New Repositories
131
131
-Write 1-2 paragraphs that curate the most credible new launches.
132
+Write 1-2 paragraphs that curate the most credible new launches. Whenever you mention a repo, use `[owner/repo](https://github.com/owner/repo)`.
133
134
## Trending This Week
135
135
-Write 1 paragraph about where attention moved. If star deltas are missing, say so clearly.
136
+Write 1 paragraph about where attention moved. If star deltas are missing, say so clearly. Whenever you mention a repo, use `[owner/repo](https://github.com/owner/repo)`.
137
138
## Trend Analysis
139
140
### Signal
141
141
-Write 1 paragraph on the durable patterns.
142
+Write 1 paragraph on the durable patterns. Whenever you mention a repo, use `[owner/repo](https://github.com/owner/repo)`.
143
144
### Noise
145
145
-Write 1 paragraph on the inflated, weak, or off-mission patterns.
146
+Write 1 paragraph on the inflated, weak, or off-mission patterns. Whenever you mention a repo, use `[owner/repo](https://github.com/owner/repo)`.
147
148
## What's Missing
149
150
### Gaps
151
151
-Write 1 paragraph on meaningful absences or underserved categories.
152
+Write 1 paragraph on meaningful absences or underserved categories. Whenever you mention a repo, use `[owner/repo](https://github.com/owner/repo)`.
153
154
## Conclusion
155
155
-Write a short closing takeaway about what the week means and what to watch next.
156
+Write a short closing takeaway about what the week means and what to watch next. Whenever you mention a repo, use `[owner/repo](https://github.com/owner/repo)`.
157
```