opensearch
claudeSearch BlazeMeter logs across denv/bzdev/ci/staging/prod — bundles a read-only opensearch-reader MCP server plus a skill that builds safe Lucene queries and condenses results.
1 skill · 1 MCP server
Base plugin with generic skill, slash-command, sub-agent, and hook templates plus working hook examples (audit logger, secret-on-write guard, skill-activation telemetry).
Plugin base-tools from marketplace coreteam-claude-base in Blazemeter/coreteam-claude-utils. Commands read from the repo's manifest — 12 days ago.
example-skillTemplate skill — copy this directory and edit. Replace this description with WHEN Claude should invoke the skill (e.g. "Use when the user asks to inspect X" or "Triggers on mentions of Y"). The description is the only signal Claude uses to auto-load the skill, so be specific about the trigger surfac
file-doc-taskFile or update a documentation-planning JIRA task for a customer-facing feature, using the documentation team's standard template. Idempotent create-or-update — safe to run early (draft a DOC-ready ticket from the specs/design to guide development) and again at finalize (reconcile the description ag
grill-meInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
jira-lifecycleKeep a related JIRA issue's status and comment trail in step with AI-driven work so the lifecycle is visible in JIRA metrics. Idempotent, forward-only transitions at each lifecycle point — move to In Progress when work starts, add progress comments for meaningful updates, post the PR link + summary
summarize-prSummarize a GitHub pull request — purpose, key changes, review state, CI status, and outstanding blockers. Use when the user pastes a PR URL (github.com/<org>/<repo>/pull/<n>), references a PR by number (e.g. "PR #123", "summarize PR 42"), or asks "what's in PR X" / "is PR X ready to merge". Do NOT
to-issuesBreak a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
/base-tools:example-commandTemplate slash command — copy this file to `commands/<your-name>.md` and edit. Replace this description with a one-line summary; it shows up in the `/` menu.
example-agentTemplate sub-agent — copy this file to `agents/<your-name>.md` and edit. Replace this description with WHEN Claude should delegate to this agent (e.g. "Investigates X using Y and Z" or "Reviews W for compliance"). Specific, action-oriented descriptions work best.
Search BlazeMeter logs across denv/bzdev/ci/staging/prod — bundles a read-only opensearch-reader MCP server plus a skill that builds safe Lucene queries and condenses results.
1 skill · 1 MCP server
Triage backend API_TESTS-CI failure noise from the BlazeMeter Slack monitoring channels: find persistent vs. flaky failures, identify the likely culprit commit, and check for an already-open PR before ever drafting a notification.
1 skill
Fix vulnerable dependencies correctly — golden rule (direct/BOM not transitive), advisory cross-check, defer breaking majors, per-stack recipes (composer/gradle/maven/pip/npm) + local build+test.
1 skill
Blazemeter GitHub branch/PR conventions — dated Docker-safe branch, commit+push via SSO gh, PR into the integration branch, tag PR title with the ticket id (in the title at creation when the ticket already exists), and a fixed PR-body template (intro + CVE table → Change → Verification ✅/⚠️/❌ → Jira → [crane only] copy-paste mend-finalize Next step, placeholders aligned on <MOB-ticket>).
1 skill
Blazemeter blazect Jenkins gate — trigger a multibranch build with PUSH_TO_GCR + PERFORM_WHITESOURCE_SCAN, gate on the specific triggered build (not lastBuild), fix-forward, never gate on API_TESTS-CI; plus deploy a green branch to denv (USERNAME=JENKINS_USER) via the shared 'Deploy environment' job and gate on it.
1 skill
Create/transition Blazemeter MOB Jira tickets — board 5348, Task, Product/Scrum-Team/Sprint fields, assignee = repo owner, status In Progress, caller-supplied labels (e.g. mend_orch), optional parent issue (parent_key in jira config), bounded 429 backoff. Ticket summary/name is caller-supplied. Can be created before a PR exists, then updated with the PR link.
1 skill
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
6 skills
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
5 skills + 35 modes + Material Passport pipeline. Includes v3.6.7 cross-model audit gate and v3.6.8 generator-evaluator contract.
5 skills · 16 commands · 4 agents · hooks
Claude Skills for Obsidian
6 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.