Automated summary
Loads the Inspire team's internal workflow documentation (development, PR, deployment, QA, frontend, Amplience CMS, test generation) to answer process questions.
Strengths
- Covers the whole chain from day-to-day development through deployment and rollback
- Points the agent at specific reference files instead of improvising answers
- Helpful for onboarding a new team member onto established conventions
Limitations
- Fully dependent on the files under ./references/ existing; one entry is misspelled (fronend_workflow.md) and may fail to load
- Read-only: it describes processes but cannot execute or enforce them
- Inspire-specific content that does not transfer to another organization
Use it whenever a question concerns an internal Inspire team convention or process, or when a new developer is getting up to speed.
Avoid it for general engineering questions or in a repository that does not contain the team's reference files.
Security analysis
SafeThe skill only declares and instructs use of the Read tool to load local reference documentation. It does not execute commands, access networks, modify files, handle secrets, or bypass safety controls, so its execution risk is minimal.
No concerns found
How this analysis is madeExamples
What's our branch naming convention, and how should I phrase the commit message for this bug fix?Walk me through everything that has to happen before my pull request can be merged on this team.A deployment just broke production — what's our rollback procedure?name: inspire-workflows description: Inspire team development workflows, deployment pipelines, and PR processes. Use when following team processes or understanding how things get done. user-invocable: false allowed-tools: Read
Inspire Team Workflows Context
When this skill is activated, load the following workflow documentation:
Required Context Files
Read these files to understand the Inspire team's workflows:
-
Development Workflow:
./references/development_workflow.md- Daily development process
- Branch naming conventions
- Commit guidelines
-
PR Process:
./references/pr-process.md- PR creation guidelines
- Review requirements
- Merge criteria
-
Deployment Pipelines:
./references/deployment_pipelines.md- CI/CD pipeline overview
- Deployment stages
- Rollback procedures
-
QA Workflow:
./references/qa_workflow.md- Testing stages
- QA sign-off process
- Bug reporting
-
Frontend Workflow:
./references/fronend_workflow.md- Frontend-specific processes
- Component development
- Design handoff
-
Amplience Workflow:
./references/amplience-workflow.md- CMS workflow
- Content management
- Publishing process
-
Testing Generation Workflow:
./references/testing-generation-workflow.md- Test generation process
- Automation guidelines
- Coverage requirements
Instructions
Before responding to workflow questions:
- Use the Read tool to load relevant files above
- Follow the team's established processes
- Reference specific workflows for guidance
When to Load This Context
- Following development processes
- Creating pull requests
- Understanding deployment
- Onboarding to the team
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/inspire-team-workflows-mm5t8ch6/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/inspire-team-workflows-mm5t8ch6' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/inspire-team-workflows-mm5t8ch6/download' --output '.skill-downloads/inspire-team-workflows-mm5t8ch6/SKILL.md.part' && mv '.skill-downloads/inspire-team-workflows-mm5t8ch6/SKILL.md.part' '.skill-downloads/inspire-team-workflows-mm5t8ch6/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/inspire-team-workflows-mm5t8ch6/SKILL.md' && test -s '.skill-downloads/inspire-team-workflows-mm5t8ch6/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/inspire-workflows' && cp -R '.skill-downloads/inspire-team-workflows-mm5t8ch6' '.claude/skills/inspire-workflows'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/inspire-team-workflows-mm5t8ch6'openskills read 'inspire-team-workflows-mm5t8ch6'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/inspire-team-workflows-mm5t8ch6/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.