trellis-before-dev-4b0609 100/100

Is trellis-before-dev-4b0609 safe to install?

SaferSkills independently audited trellis-before-dev-4b0609 (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.

.agents/skills/trellis-before-dev/SKILL.md · 1 file

.agents/skills/trellis-before-dev/SKILL.md1.5 KB · Markdown

name: trellis-before-dev

description: "Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards."

Read the relevant development guidelines before starting your task.

Execute these steps:

Discover packages and their spec layers:

   python3 ./.trellis/scripts/get_context.py --mode packages

Identify which specs apply to your task based on:

Which package you're modifying (e.g., cli/, docs-site/)
What type of work (backend, frontend, unit-test, docs, etc.)

Read the spec index for each relevant module:

   cat .trellis/spec/<package>/<layer>/index.md

Follow the "Pre-Development Checklist" section in the index.

Read the specific guideline files listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g., error-handling.md, conventions.md, mock-strategies.md). Read those files to understand the coding standards and patterns.

Always read shared guides:

   cat .trellis/spec/guides/index.md

Understand the coding standards and patterns you need to follow, then proceed with your development plan.

This step is mandatory before writing any code.

trellis-before-dev-4b0609— agent skill

Is trellis-before-dev-4b0609 safe to install?

Audit the pieces. Scan the whole. Decide.