Skip to content
Skills Library
Programming · Review & audit

validate-selector

/validate-selector

Audit a Sim dynamic selector across its declaration, browser-safe manifest, server attachment, provider primitive, and selectors.execute security boundary. Use when reviewing selector correctness, secret handling, scope authorization, or dead selector-only routes.

Repository
sim ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Audit a Sim dynamic selector across its declaration, browser-safe manifest, server attachment, provider primitive, and selectors.execute security boundary. Use when reviewing selector correctness, secret handling, scope authorization, or dead selector-only routes.

Arguments

/validate-selector <selector-key-or-service>
Original author description

Audit a Sim dynamic selector across its declaration, browser-safe manifest, server attachment, provider primitive, and selectors.execute security boundary. Use when reviewing selector correctness, secret handling, scope authorization, or dead selector-only routes.

How it works

  1. Gather the path
  2. Validate the declaration and manifest
  3. Validate the server boundary
  4. Validate provider reuse and browser boundaries
  5. Tests and report
Original SKILL.md headings · 96 lines, 607 words
SKILL.md preview
---
name: validate-selector
description: Audit a Sim dynamic selector across its declaration, browser-safe manifest, server attachment, provider primitive, and selectors.execute security boundary. Use when reviewing selector correctness, secret handling, scope authorization, or dead selector-only routes.
argument-hint: <selector-key-or-service>
---

# Validate Selector

Validate the complete path, not only the provider adapter.

## Gather the path

Read:

- Every block, trigger, and connector field using the selector key.
- `apps/sim/lib/selectors/manifest.ts` and `types.ts`.
- `apps/sim/lib/selectors/context.ts`.
- The matching server attachment and any shared provider listing primitive.
- `apps/sim/lib/selectors/server/registry.ts`.
- The shared application executor, route contract, client transport, and focused tests when the
  finding concerns shared behavior.

Search literal API paths as well as TypeScript imports before deciding whether an old provider route
or contract is unused.

## Validate the declaration and manifest

- The key has exactly one classification and one attachment (`local` keys use the local registry).
- Allowed context is minimal and readiness matches the provider request.
- List, pagination, search, detail, unknown-detail, scope, and stale-time metadata match actual UX.
- `dependsOn` names the required source fields; canonical pairs contribute only their active member.
- Action/trigger and connector surfaces build the same canonical context.
- Exact `{{KEY}}` references remain unresolved in the browser; runtime references are omitted,
  while embedded interpolation is forwarded unresolved and rejected by the server executor.
- Query keys contain no context value, reference, credential ID, secret, or hash of one.

## Validate the server boundary

For provider and internal selectors, confirm the shared executor owns this order:

1. Session authentication before request parsing.
2. Canonical workflow/workspace loading and read authorization.
3. Manifest capability and exact-context allowlisting.
4. Exact environment-reference resolution on the server.
5. Credential use, workspace, and trusted provider/service binding.
6. Destination-policy enforcement before provider network access.
7. Provider/internal execution followed by explicit option projection and sanitization.

The attachment must not duplicate these shared checks. It must not accept a browser-provided module,
provider, service, operation kind, origin, or scope list.

Review its destination classification:

- `fixed` origins are code-defined.
- `credential-bound` origins are derived from or checked against the authorized credential.
- `user-controlled` destinations have an explicit policy for hidden use-only authentication and
  network safety.

Missing and inaccessible references, and missing, unauthorized, or provider-mismatched credentials,
must not become existence oracles. Hidden/server-only resolved plaintext, credentials, authentication
material, and raw upstream errors must not enter responses, query/cache/rate keys, selector result
caches, logs, audit metadata, redirects, or error messages. Browser-known literals and viewable
personal/shared values are not automatically protected plaintext, but the executor must still never
deliberately or wholesale echo selector context. Only intentionally projected, normalized
`{ id, label, meta? }` options and bounded cursors may cross the boundary.

Selector code adds no context, token, or result cache beyond the single accepted exception
described in the `add-selector` skill ("Wire the UI declaration").

## Validate provider reuse and browser boundaries

- The attachment calls a server-only provider primitive, not a route handler or internal HTTP URL.
- A surviving provider route has a proven non-selector caller and delegates to the same primitive.
- There is no client provider selector module, selector-specific token request, or browser request to
  a provider-specific selector route.
- Internal selectors delegate to existing authorized use cases rather than querying protected data
  in the route or adapter.

## Tests and report

Use existing Vitest/route/React Query patterns. Preserve valuable provider tests, but do not demand a
per-selector authorization matrix. Shared executor tests should cover ordering, references,
credential binding, sanitization, and safe errors; adapter tests should cover only special provider
behavior.

Report critical, warning, and suggestion findings. Treat browser secret resolution, missing scope or
credential authorization, unsafe destination binding, provider payload passthrough, and plaintext
egress as critical.

Run the smallest relevant focused suites plus:

```bash
bun run --cwd apps/sim type-check
bun run check:api-validation:strict
bun run check:fork-dependent-coverage
bun run check:client-boundary
git diff --check
```

State which live-provider checks remain pending when disposable credentials are unavailable.
Files in this package (2)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named validate-selector.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 9de70ddfd8b7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100add-selector
    Add or update a Sim dynamic selector using the shared manifest, server attachment, and selectors.execute path. Use for provider-backed, internal, or local option lists referenced by block, trigger, or connector selectorKey fields.
  • 90azure-role-selector
    Plan, implement, or review azure role selector work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests azure role selector work.
  • 100has-selector
    Use when reviewing stylesheets or components that use JavaScript to toggle classes on parent elements based on child state, form input values, or content presence — :has() may replace the JavaScript entirely.
  • 100wp-style-engine
    Generate and audit block-style CSS with WordPress's public Style Engine functions. Covers wp_style_engine_get_styles, wp_style_engine_get_stylesheet_from_css_rules, wp_style_engine_get_stylesheet_from_context, style objects, preset tokens, selectors, rule groups, request-local…
  • 90quality-engineering-selector-stability
    Cross-stack selector and test-id policy for web and mobile automation. Use when writing or reviewing E2E/UI test locators, or adding data-testid/accessibility identifiers to components.
  • 100selector-drift-recovery
    Bulk-regenerate broken test selectors after a UI refactor or redesign. Detects drift between old and new DOM with an aria-snapshot diff, maps old locators to new equivalents using role-first + region scoping, validates against the new build, and produces a single PR with grouped…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.