Index of every page on this site: llms.txt
All skills
pingdotgg avatar

/vendored-assets

@b5453de
by Ping.ggpingdotgg/t3code67k stars
11,639
Run it yourself

Vendored assets. Use when importing or updating checked-in third-party or externally generated JavaScript, CSS, registries, schemas, snapshots, or Scalar, Swagger, and MIME artifacts.

  • 2 files
  • 3.4 KB
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/pingdotgg/t3code/vendored-assets

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈50 tokens for metadata: the name and description. ≈677 when used: this file. ≈128 more on demand in 1 file.

Description uses 2.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈201 characters, or 2.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Treat upstream artifacts as supply-chain inputs. Change their generator or documented import source, then regenerate; generated output is review evidence, not an editing surface.

Workflow

  1. Trace ownership. Identify the artifact, generator or exact import procedure, upstream source/version, license, consumers, tests, and shipped package or bundle. Search by asset and upstream project name to find current packaging scripts, generated artifacts, consumers, and history. Continue when every input and consumer is accounted for.
  2. Pin provenance. Resolve moving URLs, tags, branches, and omitted versions to an immutable release or artifact. Record project, version, path or URL, and digest in the generator or maintenance header. Omit a digest only when another enforced immutable source is recorded. Continue when a future run cannot silently select different bytes.
  3. Clear the license gate. Verify release metadata, license files, bundled notices, and the license trail retained in the distributed form. Continue when every distributed artifact has a verified retained license trail.
  4. Regenerate. Improve the generator or import reference first. Recover an exact procedure for generatorless assets; add a deterministic script only for recurring updates. Record a one-off procedure beside the artifact. A clean rerun must produce no diff.
  5. Audit the complete diff. Account for behavior, URLs and runtime fetches, source maps, notices, encoding, format changes, and additions or removals. For browser assets, also read browser-assets.md. Continue when every change is attributable and suspicious content is resolved or reported.
  6. Clear test and size gates. Record byte sizes before and after, use focused consumer tests, and compare bundle size or composition when shipped JavaScript, CSS, or registry output changes materially. Compare that output against the pre-update revision rather than measuring only current size. Continue when focused checks pass and every non-trivial size delta is explained.
  7. Close release impact. Apply root changeset routing for consumer-visible behavior, browser support, wire data, or meaningful shipped-size changes. Generated sections owned by barrels, AI docs, or migration tooling remain with the owners named in root instructions.

The task is complete when every input and consumer is accounted for, provenance and licenses are immutable and retained, regeneration is deterministic, every output change and non-trivial size delta is explained, focused checks pass or are reported as not runnable, and release impact is recorded.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at b5453de. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago

README badge

README badge for pingdotgg/t3code/vendored-assets