Generate well-structured user stories for Enterspeed using the standard team template. Use when someone describes a feature, capability, or user role + goal and needs a formatted user story. Works from rough ideas or specific role+goal inputs. Do not use for bug fixes, technical debt, or retrospective analysis.
Invoke automatically at the start of any gitflow-release-* or gitflow-hotfix-* workflow. Verifies git flow installation, initialisation, git user identity, clean working directory, and branch state.
Finish a git flow release once the master PR is merged: verifies PR state, tags master, opens a back-merge PR from master to develop, and cleans up the release branch. Use when the user says "finish the release", "the master PR is merged", "after merging the PR", or "tag the release". Always run after gitflow-release-publish. This is the final step in the release workflow.
Analyse unreleased commits and propose a semantic version bump for an Enterspeed project. Use when the user says "prepare a release", "what should the next version be", "check what's unreleased", or "propose a version bump". Run this before gitflow-release-start to review the proposed version before any changes are made.
Push a prepared git flow release branch and open a PR to master. Use when the user says "publish the release", "push the release branch", "open the PR", or after gitflow-release-start completes. Requires the release branch to already exist locally with the version commit. Follow up with gitflow-release-finish once the master PR is merged.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Shared AI agent skills for the Enterspeed team, distributed as a Claude Code marketplace.
From your terminal, run:
claude plugin marketplace add https://github.com/enterspeedhq/agent-skills
claude plugin install enterspeed@enterspeed
Note: Once org-managed settings are fully configured, this step will happen automatically for all team members. Until then, each person runs the commands above once.
Skills are added via pull requests. When a new skill is merged, the plugin version is bumped and Claude Code will auto-update at next startup — no action needed.
To manually trigger an update:
claude plugin marketplace update enterspeed
claude plugin update enterspeed@enterspeed
Note: The marketplace name is
enterspeed(not the full GitHub URL). Run both commands — the first refreshes the index from GitHub, the second installs the latest version.
Every skill has a SKILL.md file and may include additional resources:
plugins/enterspeed/skills/<skill-name>/
├── SKILL.md # Required: skill definition
├── scripts/ # Optional: helper scripts
│ └── <script-file>
├── templates/ # Optional: templates or config files
└── <other-resources> # Optional: test data, fixtures, etc.
The SKILL.md must start with:
---
name: your-skill-name
description: When to trigger this skill — be specific, this is what Claude reads to decide whether to use it.
---
Followed by the skill body: instructions, context, templates, or anything Claude should know when the skill activates.
mainplugins/enterspeed/skills/<skill-name>/SKILL.md.claude-plugin/marketplace.json (e.g. 1.2.0 → 1.3.0)description field is critical — it's how Claude decides when to invoke your skill. Be explicit about trigger phrases and use cases.shortcut-demo-planner for an example).SKILL.md under the same directory.agent-skills/
├── .claude-plugin/
│ └── marketplace.json # Marketplace definition + version
└── plugins/
└── enterspeed/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata
└── skills/
└── <skill-name>/
└── SKILL.md
GitHub Copilot automatically loads Agent Skills placed in any of the standard skill folders:
Project skills:
.github/skills/, .claude/skills/, .agents/skills/ [github.com]
Personal/global skills:
~/.copilot/skills/, ~/.claude/skills/, ~/.agents/skills/ [github.com]
Place (or symlink) your skills/ folder into one of these locations and Copilot will detect it automatically.
Rider supports Copilot Skills but cannot add custom folders.
You must use one of the standard Copilot skill directories.
You can set this up in two ways:
If your skills live in a Git repo, create a symlink into one of the supported directories so changes update automatically.
Windows
cmd /c mklink /D "%USERPROFILE%\.copilot\skills\my-skills" "C:\path\to\repo\skills"
macOS / Linux
ln -s "/path/to/repo/skills" ~/.copilot/skills/my-skills
Restart Rider and the skills will load.
Move your skill folders into:
~/.copilot/skills/
~/.claude/skills/
~/.agents/skills/
VS Code supports the same standard skill folders as Rider and additionally allows you to add extra skill locations.
Use the same symlink method as Rider to link your repo to a supported directory.
skills/ directory livesVS Code will now scan and load skills from that location.
npx claudepluginhub enterspeedhq/agent-skills --plugin enterspeedSanity plugin for Claude Code with MCP server, agent skills, agent rules, and slash commands.
Agent skills for Contentful apps, APIs, migrations, and personalization
Claude Code skill pack for Webflow (24 skills)
Full RampStack catalog of website-lifecycle skills across research, brand, build, and audit.
Create skills from documentation folders and project codebases. Review, test, and package Anthropic Agent Skills for Claude.ai and Claude Code. 13 commands including from-docs, from-project, beginner tutorial, interactive wizard, templates, quality auditing, and distribution packaging.
The Hitchhiker's Guide — content creation suite with automated pipeline, daily briefs, and blog writing