Skip to content

Update factory authoring skill to recommend automation scope filters #16670

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MaggieShan merged 4 commits into from
Oct 28, 2026
Merged

Update factory authoring skill to recommend automation scope filters #16670

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f06c4b8
docs: recommend scope filters when authoring factory automations
warp-agent-staging[bot] Oct 28, 2026
7b5ed7b
docs: align scope guidance with factory client recommendations
warp-agent-staging[bot] Oct 28, 2026
97343fb
docs: condense automation scope guidance into one bullet
warp-agent-staging[bot] Oct 28, 2026
0b4f421
docs: explain rationale for automation scope filters
warp-agent-staging[bot] Oct 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions resources/bundled/skills/factory-files/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,6 +161,12 @@ read them.
its canonical key, and declaring both is an error. The Linear and Slack ones
name objects the server looks up at apply time, so they take a plain list of
names rather than an `in`/`not_in` matcher.
- When creating automations, recommend non-empty inclusive scope filters to
focus on intended work and avoid noisy, unnecessary agent runs and resource
use from unrelated activity: GitHub `labels` for events that support labels,
Linear `teams` (or `team_ids`), Jira `project_keys`, and Microsoft Teams
`team_ids`. Follow the event's schema, ask if scope is unclear, and confirm
intentional broad matching; these recommendations do not block saving.
- A webhook never carries secret material. `secretName` is required in every
`authMode` and names an existing managed secret; the server does not generate
a secret for a file-declared source, because nothing could then read it back
Expand Down
Loading