> ## Documentation Index
> Fetch the complete documentation index at: https://gleanfeed.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Install agent skills

> Add optional Glean Feed workflows for changelog drafting, feature evaluation, and feedback triage to a coding agent.

Agent skills give your coding agent repeatable ways to use the Glean Feed MCP tools. Install only the workflows you want; each skill runs in your agent and uses the repository and MCP connections you approve.

These are agent workflows, not background integrations. Glean Feed does not receive your repository credentials, read your codebase directly, or run the skills on its servers.

## Before you install

You need:

* An agent that supports Agent Skills.
* A [Glean Feed MCP connection](/api/mcp) approved for the target workspace.
* GitHub tools, GitHub MCP, or local repository access for workflows that inspect code.

Start with read scopes. Add a write scope only when you want the agent to perform the matching action.

## Choose skills interactively

Run the package install command, then select the workflows you want:

```bash theme={null}
npx skills add MSW-Digital/glean-feed-skills
```

## Install one skill

<CodeGroup>
  ```bash Changelog drafting theme={null}
  npx skills add MSW-Digital/glean-feed-skills --skill github-prs-to-glean-changelog
  ```

  ```bash Feature evaluation theme={null}
  npx skills add MSW-Digital/glean-feed-skills --skill evaluate-feature-request
  ```

  ```bash Feedback triage theme={null}
  npx skills add MSW-Digital/glean-feed-skills --skill triage-product-feedback
  ```
</CodeGroup>

You can review the skill source in the [public GitHub repository](https://github.com/MSW-Digital/glean-feed-skills) before installing it.

## Pick a workflow

### Draft changelogs from GitHub PRs

`github-prs-to-glean-changelog` reads a GitHub release window, separates customer-visible changes from internal work, and proposes outcome-led Glean Feed entries. It can connect entries to related feedback when confident matches exist.

Required access:

* GitHub read access.
* `changelog:read` to inspect existing entries.
* `changelog:write` only after you approve creating drafts or publishing.
* Optional `feedback:read` and `roadmap:read` for related customer and delivery evidence.

<Prompt description="Draft Glean Feed updates from merged GitHub PRs." icon="git-pull-request" actions={["copy", "cursor"]}>
  Review merged pull requests since our last release and propose customer-facing Glean Feed
  changelog entries. Show me the exact title, body, source PRs, tags, and linked feedback before
  creating drafts. Do not publish until I approve the stored drafts in a separate step.
</Prompt>

### Evaluate a feature request

`evaluate-feature-request` compares a proposed request with Glean Feed feedback, roadmap work, shipped updates, and the current repository. It returns a supported verdict—pursue now, validate first, defer, decline, or already addressed—without changing workspace data.

Recommended access:

* `feedback:read`, `roadmap:read`, `changelog:read`, and `workspace:read`.
* Repository access for current behavior, affected product areas, tests, and constraints.

<Prompt description="Evaluate a request against customer and code evidence." icon="scale" actions={["copy", "cursor"]}>
  Evaluate whether this feature request is worth pursuing. Compare it with our repository, related
  Glean Feed feedback, existing roadmap work, and shipped changelog entries. Cite the evidence, name
  the strongest counterargument, and recommend the next decision. Do not change anything.
</Prompt>

### Triage product feedback

`triage-product-feedback` groups a selected feedback inbox by customer problem, identifies high-confidence duplicate candidates, separates request types, and recommends a next action for every inspected request. It does not merge, move, or reply to requests.

Recommended access:

* `feedback:read`.
* Optional `roadmap:read`, `changelog:read`, and repository access for overlap checks.

<Prompt description="Turn recent feedback into themes and next actions." icon="list-checks" actions={["copy", "cursor"]}>
  Triage the 50 most recent Glean Feed requests. Group them by customer problem, identify
  high-confidence duplicate candidates, and recommend the next action for every request. Compare the
  themes with current roadmap and changelog work when available. Do not change anything.
</Prompt>

## Review write actions

The evaluation and triage skills are read-only. The changelog skill shows the complete customer-facing text before it creates a draft. Publishing requires another explicit approval after the stored draft is shown because first publication can email subscribed customers.

## Next steps

<Columns cols={2}>
  <Card title="Connect over MCP" icon="https://mintcdn.com/gleanfeed/XujswKjVl9A7LyQN/icons/link.svg?fit=max&auto=format&n=XujswKjVl9A7LyQN&q=85&s=75ae28db135b545c47854a349f085815" href="/api/mcp" width="24" height="24" data-path="icons/link.svg">
    Connect Glean Feed and approve a workspace.
  </Card>

  <Card title="Scopes" icon="https://mintcdn.com/gleanfeed/XujswKjVl9A7LyQN/icons/key.svg?fit=max&auto=format&n=XujswKjVl9A7LyQN&q=85&s=bef0e09f655d6e92652b5049ef64ab72" href="/api/scopes" width="24" height="24" data-path="icons/key.svg">
    Review the access each workflow needs.
  </Card>
</Columns>