influxdata
- 14 skills
- 0 followers
- 17 hours ago last updated
- ▌ Docs Testing · influxdataTesting decision guide for agents working in docs-v2. Maps changed file types to the exact test commands to run, documents what runs automatically in hooks and CI, and flags coverage gaps. Load Part 1 for the decision table; load later parts only when executing a specific test type.
- ▌ Vale Linting · influxdataRun, debug, and maintain Vale style linting for InfluxData documentation: run Vale, interpret alerts, manage vocabulary, configure product-specific .vale.ini files, and understand which rules are enabled and why. Use when running Vale, investigating or fixing Vale warnings, adding accept/ignore vocabulary terms, or setting up a product config. To author custom rule patterns and regex, see vale-rule-config.
- ▌ AI Visibility · influxdataReview documentation PRs, pages, or navigation for visibility to AI consumers — crawlers building training corpora, RAG retrievers, and autonomous agents — across the model lifecycle (pre-training, training, post-training, inference/RAG). Use whenever the user asks how docs appear to LLMs or AI agents, asks to review a PR or page for AI visibility, discoverability, GEO, or agent experience, or mentions llms.txt, llms-full.txt, markdown twins, JSON-LD, canonical links, sitemap-md, or "how would a model navigate this" — even if they don't say "AI visibility" explicitly. Also covers SEO-relevant frontmatter review (titles, descriptions, canonicals) since the same metadata drives both search snippets and AI retrieval.
- ▌ Content Editing · influxdataCreate, edit, and validate InfluxData documentation. Manages Hugo shared content across InfluxDB products, runs Vale style linting and Hugo builds, validates frontmatter and code blocks, and fact-checks via the documentation MCP server. Use when creating new doc pages, editing markdown .md files, managing shared content, running Vale or Hugo builds, or testing InfluxDB, Telegraf, or Flux documentation.
- ▌ Vale Rule Config · influxdataAuthor and test custom Vale rules for InfluxData documentation: rule types (existence, substitution, conditional), the regexp2 engine and PCRE lookarounds, and testing rule patterns in isolation. Use when writing a new Vale rule, debugging why a rule pattern does not match, or working with Vale regex. To run Vale, manage vocabulary, or fix flagged content, see vale-linting.
- ▌ Docs CLI Workflow · influxdataGuides when to use the docs create/edit CLI tools versus direct file editing for InfluxData documentation. Use when deciding whether to scaffold new pages with docs create, open existing pages with docs edit, or edit Markdown files directly.
- ▌ Exec Plan Writing · influxdataCapture durable goal, intent, and decisions for a unit of work as an execution plan under docs/exec-plans/. Use when finishing a non-trivial change that needs a decision record, when a PR closes one or more issues and the rationale would otherwise live only in commit messages or PR descriptions, or when the user asks to write an exec-plan, decision doc, or to document the why behind a change. Distinct from PLAN.md (ephemeral, scrubbed by CI on merge) and design-docs (architectural).
- ▌ Hugo Template Dev · influxdataHugo template development for InfluxData docs-v2, enforcing build and runtime testing to catch template errors that build-only validation misses. Use when creating or editing Hugo layouts, partials, or shortcodes, debugging template errors, or accessing site data in templates.
- ▌ Cypress E2e Testing · influxdataRun, validate, and analyze Cypress E2E tests for the InfluxData documentation site. Covers Hugo server management, test execution modes, and failure analysis. Use when writing or running Cypress tests, verifying rendered pages, checking JSON-LD/structured data, or debugging E2E failures after template, layout, or content changes.
- ▌ Issue Investigation · influxdataInvestigate GitHub issues before attempting fixes. Verifies reported problems are real and reproducible, checks whether fixes already exist, and gathers root cause evidence. Use before working on any bug report, broken link, or content issue.
- ▌ Influxdb3 Test Setup · influxdataSet up InfluxDB 3 Core and Enterprise instances for running documentation code block tests. Handles service initialization, worktree-specific databases, and test environment configuration. Use when preparing to run InfluxDB 3 code block tests, starting Core or Enterprise instances, or configuring .env.test and worktree-specific test databases.
- ▌ Release · influxdataThis skill should be used when the user asks to "cut a release", "publish a new version", "tag vX.Y.Z", "release the MCP server", or needs to bump the version and ship it. Covers the version-bump PR, tagging, and publishing the GitHub release; npm and Docker Hub publish run automatically from there.
- ▌ Testing · influxdata bundleThis skill should be used when the user asks to "run tests", "run the test suite", "check test results", "why are tests failing", "debug test failures", "add a test", "write a test", "update EXPECTED_TOOL_COUNT", "run protocol tests", "run integration tests", "test against InfluxDB", or needs to run, analyze, extend, or troubleshoot the MCP server test suite.
- ▌ Build Run Core Enterprise · influxdata bundleThis skill should be used when the user asks to "build the MCP server", "run the server", "set up for InfluxDB Core", "set up for InfluxDB Enterprise", "configure the server", "start the MCP server", "run with Docker", "test the MCP server connection", "use the MCP inspector", "set up .env", "what npm commands are available", or needs to build, configure, run, or troubleshoot this MCP server against InfluxDB 3 Core or InfluxDB 3 Enterprise.