Add a skill for the weekly product updates by rdimitrov · Pull Request #552 · stacklok/docs-website

rdimitrov · 2026-02-13T23:28:21Z

Description

The following PR adds a skill for the weekly product updates (applied the feedback to look only at the PRs included in the release changelogs)

Type of change

New documentation
Documentation update
Bug fix (typo, broken link, etc.)
Navigation/structure change

Related issues/PRs

Screenshots

Submitter checklist

Content and formatting

I have reviewed the content for technical accuracy
I have reviewed the content for spelling, grammar, and style

Navigation

New pages include a frontmatter section with title and description at a minimum
Sidebar navigation (sidebars.ts) updated for added, deleted, reordered, or renamed files
Redirects added to vercel.json for moved, renamed, or deleted pages (i.e., if the URL slug changed)

Reviewer checklist

Content

I have reviewed the content for technical accuracy
I have reviewed the content for spelling, grammar, and style

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>

vercel · 2026-02-13T23:28:25Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs-website	Ready	Preview, Comment	Feb 13, 2026 11:28pm

Copilot

Pull request overview

This PR adds a comprehensive Claude skill for generating weekly product updates by analyzing GitHub releases and transforming technical changes into marketing-ready content. The skill provides detailed guidance on terminology, workflow steps, output formatting, and content guidelines to ensure consistent, benefit-focused updates for the ToolHive project.

Changes:

Added .claude/skills/weekly-product-updates/SKILL.md with complete workflow for generating weekly product updates from GitHub releases
Includes repository mapping, date range handling, PR filtering logic, and two output formats (summary and blog)
Provides comprehensive content guidelines covering tone, structure, and common pitfalls

Copilot · 2026-02-13T23:34:09Z

.claude/skills/weekly-product-updates/SKILL.md

+```bash
+if [ -z "$ARGUMENTS" ] || [ "$ARGUMENTS" = "last-week" ]; then
+  END_DATE=$(date +%Y-%m-%d)
+  START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)
+else
+  START_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f1)
+  END_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f3)
+fi
+echo "Analyzing: $START_DATE to $END_DATE"
+```


The bash script examples use variables like $ARGUMENTS, $START_DATE, and $END_DATE without proper quoting in some places. While this is example code, it's good practice to quote variables to prevent word splitting and globbing issues. Consider adding quotes around variable expansions, e.g., "$ARGUMENTS", especially when the values could contain spaces or special characters.

Copilot · 2026-02-13T23:34:09Z

.claude/skills/weekly-product-updates/SKILL.md

+if [ -z "$ARGUMENTS" ] || [ "$ARGUMENTS" = "last-week" ]; then
+  END_DATE=$(date +%Y-%m-%d)
+  START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)
+else
+  START_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f1)
+  END_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f3)
+fi


The argument parsing logic is described (line 26) but the bash script example (lines 55-64) doesn't show how to extract the format argument (summary or blog) from $ARGUMENTS. Consider adding an example showing how to parse both the format and date range from the arguments, e.g., checking if the first word is 'blog' or 'summary' and then extracting the remaining arguments as the date range.

Suggested change

if [ -z "$ARGUMENTS" ] || [ "$ARGUMENTS" = "last-week" ]; then

END_DATE=$(date +%Y-%m-%d)

START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)

else

START_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f1)

END_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f3)

fi

# Default format and date range

FORMAT="summary"

DATE_RANGE="$ARGUMENTS"

# If the first word is "summary" or "blog", treat it as the format

if [ -n "$ARGUMENTS" ]; then

FIRST_WORD="${ARGUMENTS%% *}"

if [ "$FIRST_WORD" = "summary" ] || [ "$FIRST_WORD" = "blog" ]; then

FORMAT="$FIRST_WORD"

# Remove the first word and leading space to get the date range (if any)

DATE_RANGE="${ARGUMENTS#"$FIRST_WORD"}"

DATE_RANGE="${DATE_RANGE# }"

fi

fi

# Determine the actual dates from the date range

if [ -z "$DATE_RANGE" ] || [ "$DATE_RANGE" = "last-week" ]; then

END_DATE=$(date +%Y-%m-%d)

START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)

else

START_DATE=$(echo "$DATE_RANGE" | cut -d'.' -f1)

END_DATE=$(echo "$DATE_RANGE" | cut -d'.' -f3)

fi

echo "Format: $FORMAT"

Copilot · 2026-02-13T23:34:09Z

.claude/skills/weekly-product-updates/SKILL.md

+- [ToolHive Runtimes](https://github.com/stacklok/toolhive/releases) (CLI and Kubernetes Operator)
+- [ToolHive Desktop UI](https://github.com/stacklok/toolhive-studio/releases)
+- [ToolHive Registry Server](https://github.com/stacklok/toolhive-registry-server/releases)


The link order and capitalization in the "Getting started" section doesn't match the actual blog posts. Existing blog posts consistently use this order: 1) ToolHive Registry Server, 2) ToolHive desktop UI, 3) ToolHive Cloud UI, 4) ToolHive runtimes. They also use lowercase "desktop UI" and "runtimes". Update this template to match the established pattern for consistency.

Suggested change

- [ToolHive Runtimes](https://github.com/stacklok/toolhive/releases) (CLI and Kubernetes Operator)

- [ToolHive Desktop UI](https://github.com/stacklok/toolhive-studio/releases)

- [ToolHive Registry Server](https://github.com/stacklok/toolhive-registry-server/releases)

- [ToolHive Registry Server](https://github.com/stacklok/toolhive-registry-server/releases)

- [ToolHive desktop UI](https://github.com/stacklok/toolhive-studio/releases)

- [ToolHive Cloud UI](https://github.com/stacklok/toolhive-cloud/releases)

- [ToolHive runtimes](https://github.com/stacklok/toolhive/releases) (CLI and Kubernetes Operator)

Copilot · 2026-02-13T23:34:10Z

.claude/skills/weekly-product-updates/SKILL.md

+- [ToolHive Runtimes](https://github.com/stacklok/toolhive/releases) (CLI and Kubernetes Operator)
+- [ToolHive Desktop UI](https://github.com/stacklok/toolhive-studio/releases)
+- [ToolHive Registry Server](https://github.com/stacklok/toolhive-registry-server/releases)
+
+You can find all ToolHive documentation on the [Stacklok documentation site](/toolhive).


The link order and capitalization in the blog format's "Getting started" section doesn't match the actual blog posts. Existing blog posts consistently use this order: 1) ToolHive Registry Server, 2) ToolHive desktop UI, 3) ToolHive Cloud UI, 4) ToolHive runtimes. They also use lowercase "desktop UI" and "runtimes", and link to "ToolHive documentation site" not "Stacklok documentation site". Update this template to match the established pattern.

Suggested change

- [ToolHive Runtimes](https://github.com/stacklok/toolhive/releases) (CLI and Kubernetes Operator)

- [ToolHive Desktop UI](https://github.com/stacklok/toolhive-studio/releases)

- [ToolHive Registry Server](https://github.com/stacklok/toolhive-registry-server/releases)

You can find all ToolHive documentation on the [Stacklok documentation site](/toolhive).

- [ToolHive Registry Server](https://github.com/stacklok/toolhive-registry-server/releases)

- [ToolHive desktop UI](https://github.com/stacklok/toolhive-studio/releases)

- [ToolHive Cloud UI](https://github.com/stacklok/toolhive-cloud-ui/releases)

- [ToolHive runtimes](https://github.com/stacklok/toolhive/releases) (CLI and Kubernetes Operator)

You can find all ToolHive documentation on the [ToolHive documentation site](/toolhive).

Copilot · 2026-02-13T23:34:10Z

.claude/skills/weekly-product-updates/SKILL.md

+
+[Repeat for each component with marketing-worthy changes. Use ### headings.]
+
+### Getting started


The "Getting started" format is inconsistent with recent blog posts. The most recent post (2026-02-02-updates.mdx) uses **Getting started** (bold text) instead of ### Getting started (H3 heading). Update the template to match the current convention.

Suggested change

### Getting started

**Getting started**

Copilot · 2026-02-13T23:34:10Z

.claude/skills/weekly-product-updates/SKILL.md

+
+[Opening paragraph: 2-3 sentences setting the theme, hinting at value without feature-listing, accessible to both open source and commercial audiences.]
+
+{/_ truncate _/}


The truncate comment syntax uses underscores instead of asterisks to avoid being interpreted as a comment in this markdown file. However, when Claude generates the actual blog post, it needs to output the correct syntax with asterisks: {/* truncate */}. Consider adding a clarifying note that the underscores should be replaced with asterisks in the actual output.

Copilot · 2026-02-13T23:34:10Z

.claude/skills/weekly-product-updates/SKILL.md

+```bash
+if [ -z "$ARGUMENTS" ] || [ "$ARGUMENTS" = "last-week" ]; then
+  END_DATE=$(date +%Y-%m-%d)
+  START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)


The date command syntax has a fallback for GNU/Linux, but the error output redirection 2>/dev/null only applies to the macOS command. If the macOS command fails, the error will still be shown before trying the GNU command. Consider restructuring to suppress errors properly: START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d 2>/dev/null)

Suggested change

START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)

START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d 2>/dev/null)

Add a skill for the weekly product updates

9be45fd

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>

Copilot AI review requested due to automatic review settings February 13, 2026 23:28

Copilot started reviewing on behalf of rdimitrov February 13, 2026 23:28 View session

Copilot AI reviewed Feb 13, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add a skill for the weekly product updates#552

Add a skill for the weekly product updates#552
rdimitrov wants to merge 1 commit intomainfrom
weekly-skill

rdimitrov commented Feb 13, 2026

Uh oh!

vercel bot commented Feb 13, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Copilot AI Feb 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

-if [ -z "$ARGUMENTS" ] || [ "$ARGUMENTS" = "last-week" ]; then
-  END_DATE=$(date +%Y-%m-%d)
-  START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)
-else
-  START_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f1)
-  END_DATE=$(echo "$ARGUMENTS" | cut -d'.' -f3)
-fi
+# Default format and date range
+FORMAT="summary"
+DATE_RANGE="$ARGUMENTS"
+# If the first word is "summary" or "blog", treat it as the format
+if [ -n "$ARGUMENTS" ]; then
+  FIRST_WORD="${ARGUMENTS%% *}"
+  if [ "$FIRST_WORD" = "summary" ] || [ "$FIRST_WORD" = "blog" ]; then
+    FORMAT="$FIRST_WORD"
+    # Remove the first word and leading space to get the date range (if any)
+    DATE_RANGE="${ARGUMENTS#"$FIRST_WORD"}"
+    DATE_RANGE="${DATE_RANGE# }"
+  fi
+fi
+# Determine the actual dates from the date range
+if [ -z "$DATE_RANGE" ] || [ "$DATE_RANGE" = "last-week" ]; then
+  END_DATE=$(date +%Y-%m-%d)
+  START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)
+else
+  START_DATE=$(echo "$DATE_RANGE" | cut -d'.' -f1)
+  END_DATE=$(echo "$DATE_RANGE" | cut -d'.' -f3)
+fi
+echo "Format: $FORMAT"


		[Repeat for each component with marketing-worthy changes. Use ### headings.]

		### Getting started


		[Opening paragraph: 2-3 sentences setting the theme, hinting at value without feature-listing, accessible to both open source and commercial audiences.]

		{/_ truncate _/}

	START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null \|\| date -d '7 days ago' +%Y-%m-%d)
	START_DATE=$(date -v-7d +%Y-%m-%d 2>/dev/null \|\| date -d '7 days ago' +%Y-%m-%d 2>/dev/null)

Conversation

rdimitrov commented Feb 13, 2026

Description

Type of change

Related issues/PRs

Screenshots

Submitter checklist

Content and formatting

Navigation

Reviewer checklist

Content

Uh oh!

vercel bot commented Feb 13, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant