{"owner":"StackStorm","repo":"st2","hasSkills":true,"totalSkillsCount":2,"totalTokensCount":1036,"categories":["anthropic-skill","plugin-manifest"],"hasMcp":false,"mcpConfig":null,"found":["contrib/default/rules/README.md","pants-plugins/README.md"],"skills":{"contrib/default/rules/README.md":"# rules\n\nThe rules folder contains rules. See [Rules](http://docs.stackstorm.com/rules.html) for specifics on writing rules.\n","pants-plugins/README.md":"## pants plugins\n\nThis directory contains StackStorm-specific plugins for pantsbuild.\n\n`pants` should be the primary entry point for development related tasks.\nThis replaces the Makefile and related scripts such that they are more discoverable.\nThe plugins here add custom goals or other logic into pants.\n\nTo see available goals, do \"pants help goals\" and \"pants help $goal\".\n\nThese plugins might be useful outside of the StackStorm project:\n- `uses_services`\n\nThese StackStorm-specific plugins might be useful in other StackStorm-related repos.\n- `pack_metadata`\n\nThese StackStorm-specific plugins are probably only useful for the st2 repo.\n- `api_spec`\n- `macros.py` (not a plugin - see pants.toml `[GLOBAL].build_file_prelude_globs`)\n- `release`\n- `sample_conf`\n- `schemas`\n\n### `api_spec` plugin\n\nThis plugin wires up pants to make sure `st2common/st2common/openapi.yaml`\ngets regenerated if needed. Now, whenever someone runs the `fmt` goal\n(eg `pants fmt st2common/st2common/openapi.yaml`), the api spec will\nbe regenerated if any of the files used to generate it has changed.\nAlso, running the `lint` goal will fail if the schemas need to be\nregenerated.\n\nThis plugin also wires up pants so that the `lint` goal runs additional\napi spec validation on `st2common/st2common/openapi.yaml` with something\nlike `pants lint st2common/st2common/openapi.yaml`.\n\n### `macros.py` macros\n\n[Macros](https://www.pantsbuild.org/docs/macros) are a pants feature\nthat can reduce \"boilerplate\"/duplication in BUILD files. The functions\ndefined in `macros.py` are available in all the BUILD files, and using\nthem looks just like using the normal BUILD targets.\n\nFor documentation about our macros, please refer to the function docstrings\nin the `macros.py` file.\n\n### `pack_metadata` plugin\n\nThis plugin adds two new targets to pants:\n- `pack_metadata`\n- `pack_metadata_in_git_submodule`\n\nThese targets include all StackStorm pack metadata files in a pack.\nPack metadata includes top-level files (`pack.yaml`, `<pack>.yaml.example`,\n`config.schema.yaml`, and `icon.png`) and metadata (`*.yaml`, `*.yml`)\nfor actions, action-aliases, policies, rules, and sensors.\n\nThis plugin also wires up the `tailor` goal, so that it will add a\n`pack_metadata(name=\"metadata\")` target wherever it finds a `pack.yaml` file.\n\nOne of the packs in this repo is in a git submodule to test our handling\nof git submodules (`st2tests/st2tests/fixtures/packs/test_content_version`).\nIf it is not checked out, then some of the tests will fail.\nIf it is not checked out, `pack_metadata_in_git_submodule` handles providing\na helpful, instructive error message as early as possible.\n\n### `release` plugin\n\nThis plugin implements the [`SetupKwargs`](https://www.pantsbuild.org/docs/plugins-setup-py)\nplugin hook that pants uses when it auto-generates a `setup.py` file whenever\nit builds a `python_distribution()` (ie a wheel or an sdist). This makes it\neasy to centralize all of the common bits of metadata that need to go in all\nthe wheels (like `author=\"StackStorm\"` or our `project_urls`).\n\n### `sample_conf` plugin\n\nThis plugin wires up pants to make sure `conf/st2.conf.sample` gets\nregenerated whenever the source files change. Now, whenever someone runs\nthe `fmt` goal (eg `pants fmt conf/st2.conf.sample`), the sample will\nbe regenerated if any of the files used to generate it have changed.\nAlso, running the `lint` goal will fail if the sample needs to be\nregenerated.\n\n### `schemas` plugin\n\nThis plugin wires up pants to make sure `contrib/schemas/*.json` gets\nregenerated whenever the source files change. Now, whenever someone runs\nthe `fmt` goal (eg `pants fmt contrib/schemas::`), the schemas will\nbe regenerated if any of the files used to generate them have changed.\nAlso, running the `lint` goal will fail if the schemas need to be\nregenerated.\n\n### `uses_services` plugin\n\nThis plugin validates that services are running if required. For example, some tests\nneed mongo, so this plugin can ensure mongo is running. If it is not running, then\nan error with instructions on how to run it are given to the user.\n\n`uses_services` has some StackStorm-specific assumptions in it, but it might be\ngeneralizable. There are several other StackStorm-specific plugins, but some of\nthem are only useful in the st2 repo.\n"},"files":{"contrib/default/rules/README.md":"# rules\n\nThe rules folder contains rules. See [Rules](http://docs.stackstorm.com/rules.html) for specifics on writing rules.\n","pants-plugins/README.md":"## pants plugins\n\nThis directory contains StackStorm-specific plugins for pantsbuild.\n\n`pants` should be the primary entry point for development related tasks.\nThis replaces the Makefile and related scripts such that they are more discoverable.\nThe plugins here add custom goals or other logic into pants.\n\nTo see available goals, do \"pants help goals\" and \"pants help $goal\".\n\nThese plugins might be useful outside of the StackStorm project:\n- `uses_services`\n\nThese StackStorm-specific plugins might be useful in other StackStorm-related repos.\n- `pack_metadata`\n\nThese StackStorm-specific plugins are probably only useful for the st2 repo.\n- `api_spec`\n- `macros.py` (not a plugin - see pants.toml `[GLOBAL].build_file_prelude_globs`)\n- `release`\n- `sample_conf`\n- `schemas`\n\n### `api_spec` plugin\n\nThis plugin wires up pants to make sure `st2common/st2common/openapi.yaml`\ngets regenerated if needed. Now, whenever someone runs the `fmt` goal\n(eg `pants fmt st2common/st2common/openapi.yaml`), the api spec will\nbe regenerated if any of the files used to generate it has changed.\nAlso, running the `lint` goal will fail if the schemas need to be\nregenerated.\n\nThis plugin also wires up pants so that the `lint` goal runs additional\napi spec validation on `st2common/st2common/openapi.yaml` with something\nlike `pants lint st2common/st2common/openapi.yaml`.\n\n### `macros.py` macros\n\n[Macros](https://www.pantsbuild.org/docs/macros) are a pants feature\nthat can reduce \"boilerplate\"/duplication in BUILD files. The functions\ndefined in `macros.py` are available in all the BUILD files, and using\nthem looks just like using the normal BUILD targets.\n\nFor documentation about our macros, please refer to the function docstrings\nin the `macros.py` file.\n\n### `pack_metadata` plugin\n\nThis plugin adds two new targets to pants:\n- `pack_metadata`\n- `pack_metadata_in_git_submodule`\n\nThese targets include all StackStorm pack metadata files in a pack.\nPack metadata includes top-level files (`pack.yaml`, `<pack>.yaml.example`,\n`config.schema.yaml`, and `icon.png`) and metadata (`*.yaml`, `*.yml`)\nfor actions, action-aliases, policies, rules, and sensors.\n\nThis plugin also wires up the `tailor` goal, so that it will add a\n`pack_metadata(name=\"metadata\")` target wherever it finds a `pack.yaml` file.\n\nOne of the packs in this repo is in a git submodule to test our handling\nof git submodules (`st2tests/st2tests/fixtures/packs/test_content_version`).\nIf it is not checked out, then some of the tests will fail.\nIf it is not checked out, `pack_metadata_in_git_submodule` handles providing\na helpful, instructive error message as early as possible.\n\n### `release` plugin\n\nThis plugin implements the [`SetupKwargs`](https://www.pantsbuild.org/docs/plugins-setup-py)\nplugin hook that pants uses when it auto-generates a `setup.py` file whenever\nit builds a `python_distribution()` (ie a wheel or an sdist). This makes it\neasy to centralize all of the common bits of metadata that need to go in all\nthe wheels (like `author=\"StackStorm\"` or our `project_urls`).\n\n### `sample_conf` plugin\n\nThis plugin wires up pants to make sure `conf/st2.conf.sample` gets\nregenerated whenever the source files change. Now, whenever someone runs\nthe `fmt` goal (eg `pants fmt conf/st2.conf.sample`), the sample will\nbe regenerated if any of the files used to generate it have changed.\nAlso, running the `lint` goal will fail if the sample needs to be\nregenerated.\n\n### `schemas` plugin\n\nThis plugin wires up pants to make sure `contrib/schemas/*.json` gets\nregenerated whenever the source files change. Now, whenever someone runs\nthe `fmt` goal (eg `pants fmt contrib/schemas::`), the schemas will\nbe regenerated if any of the files used to generate them have changed.\nAlso, running the `lint` goal will fail if the schemas need to be\nregenerated.\n\n### `uses_services` plugin\n\nThis plugin validates that services are running if required. For example, some tests\nneed mongo, so this plugin can ensure mongo is running. If it is not running, then\nan error with instructions on how to run it are given to the user.\n\n`uses_services` has some StackStorm-specific assumptions in it, but it might be\ngeneralizable. There are several other StackStorm-specific plugins, but some of\nthem are only useful in the st2 repo.\n"},"items":[{"name":"README.md","path":"contrib/default/rules/README.md","rawUrl":"https://raw.githubusercontent.com/StackStorm/st2/HEAD/contrib/default/rules/README.md","title":"Rules Skill","category":"anthropic-skill","format":"markdown","content":"# rules\n\nThe rules folder contains rules. See [Rules](http://docs.stackstorm.com/rules.html) for specifics on writing rules.\n","isInternal":false,"tokens":28,"sizeBytes":125},{"name":"README.md","path":"pants-plugins/README.md","rawUrl":"https://raw.githubusercontent.com/StackStorm/st2/HEAD/pants-plugins/README.md","title":"pants-plugins Documentation","category":"plugin-manifest","format":"markdown","content":"## pants plugins\n\nThis directory contains StackStorm-specific plugins for pantsbuild.\n\n`pants` should be the primary entry point for development related tasks.\nThis replaces the Makefile and related scripts such that they are more discoverable.\nThe plugins here add custom goals or other logic into pants.\n\nTo see available goals, do \"pants help goals\" and \"pants help $goal\".\n\nThese plugins might be useful outside of the StackStorm project:\n- `uses_services`\n\nThese StackStorm-specific plugins might be useful in other StackStorm-related repos.\n- `pack_metadata`\n\nThese StackStorm-specific plugins are probably only useful for the st2 repo.\n- `api_spec`\n- `macros.py` (not a plugin - see pants.toml `[GLOBAL].build_file_prelude_globs`)\n- `release`\n- `sample_conf`\n- `schemas`\n\n### `api_spec` plugin\n\nThis plugin wires up pants to make sure `st2common/st2common/openapi.yaml`\ngets regenerated if needed. Now, whenever someone runs the `fmt` goal\n(eg `pants fmt st2common/st2common/openapi.yaml`), the api spec will\nbe regenerated if any of the files used to generate it has changed.\nAlso, running the `lint` goal will fail if the schemas need to be\nregenerated.\n\nThis plugin also wires up pants so that the `lint` goal runs additional\napi spec validation on `st2common/st2common/openapi.yaml` with something\nlike `pants lint st2common/st2common/openapi.yaml`.\n\n### `macros.py` macros\n\n[Macros](https://www.pantsbuild.org/docs/macros) are a pants feature\nthat can reduce \"boilerplate\"/duplication in BUILD files. The functions\ndefined in `macros.py` are available in all the BUILD files, and using\nthem looks just like using the normal BUILD targets.\n\nFor documentation about our macros, please refer to the function docstrings\nin the `macros.py` file.\n\n### `pack_metadata` plugin\n\nThis plugin adds two new targets to pants:\n- `pack_metadata`\n- `pack_metadata_in_git_submodule`\n\nThese targets include all StackStorm pack metadata files in a pack.\nPack metadata includes top-level files (`pack.yaml`, `<pack>.yaml.example`,\n`config.schema.yaml`, and `icon.png`) and metadata (`*.yaml`, `*.yml`)\nfor actions, action-aliases, policies, rules, and sensors.\n\nThis plugin also wires up the `tailor` goal, so that it will add a\n`pack_metadata(name=\"metadata\")` target wherever it finds a `pack.yaml` file.\n\nOne of the packs in this repo is in a git submodule to test our handling\nof git submodules (`st2tests/st2tests/fixtures/packs/test_content_version`).\nIf it is not checked out, then some of the tests will fail.\nIf it is not checked out, `pack_metadata_in_git_submodule` handles providing\na helpful, instructive error message as early as possible.\n\n### `release` plugin\n\nThis plugin implements the [`SetupKwargs`](https://www.pantsbuild.org/docs/plugins-setup-py)\nplugin hook that pants uses when it auto-generates a `setup.py` file whenever\nit builds a `python_distribution()` (ie a wheel or an sdist). This makes it\neasy to centralize all of the common bits of metadata that need to go in all\nthe wheels (like `author=\"StackStorm\"` or our `project_urls`).\n\n### `sample_conf` plugin\n\nThis plugin wires up pants to make sure `conf/st2.conf.sample` gets\nregenerated whenever the source files change. Now, whenever someone runs\nthe `fmt` goal (eg `pants fmt conf/st2.conf.sample`), the sample will\nbe regenerated if any of the files used to generate it have changed.\nAlso, running the `lint` goal will fail if the sample needs to be\nregenerated.\n\n### `schemas` plugin\n\nThis plugin wires up pants to make sure `contrib/schemas/*.json` gets\nregenerated whenever the source files change. Now, whenever someone runs\nthe `fmt` goal (eg `pants fmt contrib/schemas::`), the schemas will\nbe regenerated if any of the files used to generate them have changed.\nAlso, running the `lint` goal will fail if the schemas need to be\nregenerated.\n\n### `uses_services` plugin\n\nThis plugin validates that services are running if required. For example, some tests\nneed mongo, so this plugin can ensure mongo is running. If it is not running, then\nan error with instructions on how to run it are given to the user.\n\n`uses_services` has some StackStorm-specific assumptions in it, but it might be\ngeneralizable. There are several other StackStorm-specific plugins, but some of\nthem are only useful in the st2 repo.\n","isInternal":false,"tokens":1008,"sizeBytes":4289}],"systemPromptSnippet":"<yakaai_skills repo=\"StackStorm/st2\">\n<!-- File: contrib/default/rules/README.md (Tokens: ~28 | Category: anthropic-skill) -->\n# rules\n\nThe rules folder contains rules. See [Rules](http://docs.stackstorm.com/rules.html) for specifics on writing rules.\n\n<!-- File: pants-plugins/README.md (Tokens: ~1008 | Category: plugin-manifest) -->\n## pants plugins\n\nThis directory contains StackStorm-specific plugins for pantsbuild.\n\n`pants` should be the primary entry point for development related tasks.\nThis replaces the Makefile and related scripts such that they are more discoverable.\nThe plugins here add custom goals or other logic into pants.\n\nTo see available goals, do \"pants help goals\" and \"pants help $goal\".\n\nThese plugins might be useful outside of the StackStorm project:\n- `uses_services`\n\nThese StackStorm-specific plugins might be useful in other StackStorm-related repos.\n- `pack_metadata`\n\nThese StackStorm-specific plugins are probably only useful for the st2 repo.\n- `api_spec`\n- `macros.py` (not a plugin - see pants.toml `[GLOBAL].build_file_prelude_globs`)\n- `release`\n- `sample_conf`\n- `schemas`\n\n### `api_spec` plugin\n\nThis plugin wires up pants to make sure `st2common/st2common/openapi.yaml`\ngets regenerated if needed. Now, whenever someone runs the `fmt` goal\n(eg `pants fmt st2common/st2common/openapi.yaml`), the api spec will\nbe regenerated if any of the files used to generate it has changed.\nAlso, running the `lint` goal will fail if the schemas need to be\nregenerated.\n\nThis plugin also wires up pants so that the `lint` goal runs additional\napi spec validation on `st2common/st2common/openapi.yaml` with something\nlike `pants lint st2common/st2common/openapi.yaml`.\n\n### `macros.py` macros\n\n[Macros](https://www.pantsbuild.org/docs/macros) are a pants feature\nthat can reduce \"boilerplate\"/duplication in BUILD files. The functions\ndefined in `macros.py` are available in all the BUILD files, and using\nthem looks just like using the normal BUILD targets.\n\nFor documentation about our macros, please refer to the function docstrings\nin the `macros.py` file.\n\n### `pack_metadata` plugin\n\nThis plugin adds two new targets to pants:\n- `pack_metadata`\n- `pack_metadata_in_git_submodule`\n\nThese targets include all StackStorm pack metadata files in a pack.\nPack metadata includes top-level files (`pack.yaml`, `<pack>.yaml.example`,\n`config.schema.yaml`, and `icon.png`) and metadata (`*.yaml`, `*.yml`)\nfor actions, action-aliases, policies, rules, and sensors.\n\nThis plugin also wires up the `tailor` goal, so that it will add a\n`pack_metadata(name=\"metadata\")` target wherever it finds a `pack.yaml` file.\n\nOne of the packs in this repo is in a git submodule to test our handling\nof git submodules (`st2tests/st2tests/fixtures/packs/test_content_version`).\nIf it is not checked out, then some of the tests will fail.\nIf it is not checked out, `pack_metadata_in_git_submodule` handles providing\na helpful, instructive error message as early as possible.\n\n### `release` plugin\n\nThis plugin implements the [`SetupKwargs`](https://www.pantsbuild.org/docs/plugins-setup-py)\nplugin hook that pants uses when it auto-generates a `setup.py` file whenever\nit builds a `python_distribution()` (ie a wheel or an sdist). This makes it\neasy to centralize all of the common bits of metadata that need to go in all\nthe wheels (like `author=\"StackStorm\"` or our `project_urls`).\n\n### `sample_conf` plugin\n\nThis plugin wires up pants to make sure `conf/st2.conf.sample` gets\nregenerated whenever the source files change. Now, whenever someone runs\nthe `fmt` goal (eg `pants fmt conf/st2.conf.sample`), the sample will\nbe regenerated if any of the files used to generate it have changed.\nAlso, running the `lint` goal will fail if the sample needs to be\nregenerated.\n\n### `schemas` plugin\n\nThis plugin wires up pants to make sure `contrib/schemas/*.json` gets\nregenerated whenever the source files change. Now, whenever someone runs\nthe `fmt` goal (eg `pants fmt contrib/schemas::`), the schemas will\nbe regenerated if any of the files used to generate them have changed.\nAlso, running the `lint` goal will fail if the schemas need to be\nregenerated.\n\n### `uses_services` plugin\n\nThis plugin validates that services are running if required. For example, some tests\nneed mongo, so this plugin can ensure mongo is running. If it is not running, then\nan error with instructions on how to run it are given to the user.\n\n`uses_services` has some StackStorm-specific assumptions in it, but it might be\ngeneralizable. There are several other StackStorm-specific plugins, but some of\nthem are only useful in the st2 repo.\n</yakaai_skills>"}