Sno Station
Sno Station is your agents' workstation: open-source software that turns the AI agents you already run into one squad on your own machine. Two heads are better than one, and they get better with every
Collect, store, and search data from any source to power your use cases with the Elastic Stack. Scale quickly from a centralized platform with out-of-the-box Elastic integrations to capture relevant i
PluginsHandlebars · GoGitHub @elasticOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Collect, store, and search data from any source to power your use cases with the Elastic Stack. Scale quickly from a centralized platform with out-of-the-box Elastic integrations to capture relevant i...
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
This repository contains sources for Elastic Integrations. Each Elastic Integration is an Elastic Package that defines how to observe a specific product with the Elastic Stack.
An Elastic Package may define configuration for the Elastic Agent as well as assets (such as Kibana dashboards and Elasticsearch index templates) for the Elastic Stack. It should also define documentation about the package. Finally, a package may also define tests to ensure that it is functioning as expected.Read the full README ↗This repository contains sources for Elastic Integrations. Each Elastic Integration is an Elastic Package that defines how to observe a specific product with the Elastic Stack.
An Elastic Package may define configuration for the Elastic Agent as well as assets (such as Kibana dashboards and Elasticsearch index templates) for the Elastic Stack. It should also define documentation about the package. Finally, a package may also define tests to ensure that it is functioning as expected.
Elastic Packages have a certain, well-defined structure. This structure is described by the Package Specification. The repository is also used for discussions about extending the specification (with proposals).
While this repository contains sources for Elastic Integrations, built Elastic Integrations are published into a storage based on Google Cloud bucket (more info here) and served up via the Package Registry. The Fleet UI in Kibana connects to the Package Registry and allows users to discover, install, and configure Elastic Packages.
Public documentation is compiled and exported to our Elastic docs.
Please review the Contributing Guide to learn how to build and develop packages, understand the release procedure and explore the builder tools.
If you're using an AI coding agent, we recommend installing the Agent skills below before you start.
More information about the CI pipelines that are available in this repository here.
Companion agent skills for building, reviewing, and maintaining Elastic integration packages are available in elastic/integration-skills. They work with Cursor, Codex, Gemini, Claude Code, and any other LLM-powered coding environment that can read skill/instruction files from a directory. Install them with:
npx skills add elastic/integration-skills
Claude Code users can instead install the skills natively as a plugin - see CLAUDE.md.