Skip to content

Conversation

@itamarsher
Copy link

No description provided.

Integrate seal-community/cli-action in fix mode with fix_mode=all
to both release.yml and validate-readme.yml workflows. The CLI step
is added after setup-go and before the build steps to apply security
fixes to dependencies.
Configure the Seal Security CLI action with:
- token: referenced from GitHub secrets (SEAL_TOKEN)
- project: workflows
The token only allows package downloads and doesn't pose a security
risk, so it can be included directly rather than via secrets.
@itamarsher itamarsher requested a review from a team as a code owner January 20, 2026 13:53
@google-cla
Copy link

google-cla bot commented Jan 20, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Create a skill that helps users integrate Seal Security CLI into their
CI pipelines. The skill:
- Asks users for their Seal Security token
- Auto-generates a unique project ID
- Detects CI platform (GitHub Actions, GitLab, Docker, or other)
- Adds appropriate Seal CLI configuration for the detected platform

Users can invoke with /seal-security to install Seal in their repos.
- Add install.sh for one-liner installation via curl
- Add README.md with installation options and usage instructions
- Support personal (~/.claude/skills/) and project-level installation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants