Is frontend-integration-yaml safe to install?

SaferSkills independently audited frontend-integration-yaml (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/frontend-integration-yaml/SKILL.md · 1 file

skills/frontend-integration-yaml/SKILL.md2.2 KB · Markdown

name: frontend-integration-yaml

description: Generate canonical FrontendIntegration YAML from a simplified single-menu authoring model for frontend-forge.

Frontend Integration YAML

Generate submit-ready FrontendIntegration YAML from a simplified authoring model with one menu and one or more pages.

When to Use

generate FrontendIntegration YAML
create a quick integration YAML from a CRD
create an iframe based FrontendIntegration YAML
convert simplified single-menu config into canonical YAML

Do Not Use

troubleshooting existing FrontendIntegration resources
managing enable/disable/delete lifecycle
inspecting JSBundle, Job, controller, or status flows
editing manifest generation rules
handling multi-menu authoring models

Required Inputs

Ask the user instead of guessing when any of these are missing:

metadata.name
menu.displayName
menu.placements[]
at least one page in pages[]
for crdTable: group, version, scope, names.plural
for iframe: key and iframe.src

Authoring Model

Use the simplified single-menu model as input to the generator:

top-level metadata
top-level spec for optional passthrough fields
top-level menu
top-level pages

Do not author canonical spec.menus[] by hand.

Workflow

Extract the simplified authoring model.
Fill only safe defaults.
Keep the model in single-menu form.
Run scripts/generate_frontend_integration.py.
Return the generated canonical YAML.

Rules

Treat the generator script as the source of truth.
Do not manually reconstruct canonical YAML when the generator is available.
Always output canonical kind: FrontendIntegration.
Always expand menu.placements[] into spec.menus[].
Always derive children from pages[].
If any placement is workspace, force all crdTable.scope values to Namespaced.
Default menu.icon to GridDuotone when it is omitted.
Do not add runtime-managed metadata unless explicitly requested.

Output

Return the generated YAML first, unless explanation is requested.
Prefer a single yaml code block.
After the YAML, always output this exact guidance line:

FrontendIntegration YAML has been generated. Reply 'apply' to deploy it directly.

frontend-integration-yaml— agent skill

Is frontend-integration-yaml safe to install?

Frontend Integration YAML

When to Use

Do Not Use

Required Inputs

Authoring Model

Workflow

Rules

Output

Audit the pieces. Scan the whole. Decide.