SkillAgentSearch skills...

package-json-scripts

package.json scripts naming. Colons only for parallel/sequential groups

Install / Use

npx skills add FixMyBerlin/rsv-info

Installs into whichever agent you are using.

About this skill
📐

Cursor Rules

Cursor IDE rules (v2)

Quality Score

48/100

Supported Platforms

Cursor

Our assessment of package-json-scripts

package-json-scripts scores 48/100 on our quality scale, 4323rd of 4,642 Development & Engineering skills we index.

Its Cursor Rules is 2.2 KB long, split into 6 sections and no code examples: moderately detailed.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
20/30
Structure
11/20
Description
12/15
Adoption
0/20
Freshness
5/15

Maintenance, license and trust

  • We could not determine when the repository was last updated.
  • Our last check on 2026-10-20 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

package-json-scripts compared with similar skills

All 4 of these similar skills score higher than package-json-scripts; compare them before choosing.

SkillScoreStarsUpdatedFormat
package-json-scripts (this skill)by FixMyBerlin480—Cursor Rules
taste-skillby Leonxlnx100108.3k2d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10068.9ktodayCLAUDE.md
claude-howtoby luongnv8910046.4ktodayCLAUDE.md
algorithmic-artby anthropics100177.9k40d agoSKILL.md

Frequently asked questions

How do I install package-json-scripts?
Run npx skills add FixMyBerlin/rsv-info. The install tabs above show the steps for each supported agent.
Which AI agents does package-json-scripts work with?
It is written for Cursor, as a Cursor Rules file. Other agents that read the same format can often use it too.
Is package-json-scripts safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is package-json-scripts still maintained?
We could not determine when the repository was last updated.

description: package.json scripts naming. Colons only for parallel/sequential groups globs: **/package.json alwaysApply: false

package.json script names

Use : only for step scripts that belong to a group run via bun run --parallel or bun run --sequential with a glob (<group>:*).

Colon groups (<group>:<step>)

  • Parent script orchestrates: bun run --parallel lint:*, bun run --sequential type-check:*
  • Step names use the group prefix: type-check:astro, lint:oxlint
  • Order steps with numeric prefixes when sequence matters

Standalone scripts (no :)

One-off commands run directly. Use kebab-case, no colon:

  • type-check, lint-check, format-check, check-pre-push

Verify scripts

| Script | Role | | --- | --- | | check | Local, before commit. --parallel type-check lint format test-run knip-warn | | check-ci | Read-only, run by CI. --parallel type-check lint-check format-check test-run | | check-pre-push | Husky pre-push. Same leaves as check but strict knip |

type-check runs type-check:astro (astro check) and then type-check:tsc with --sequential. Keep TypeScript 6 until astro check supports TypeScript 7.

lint and lint-check each have three steps: oxlint, lint:steckbriefe / lint-check:steckbriefe (pages load Steckbriefe only through getPublishedSteckbriefe()), and lint:map-images / lint-check:map-images (every Trassenscout geometry has a committed public/rsv-map-images/<slug>.png).

Prefer parallel groups over &&

Do not chain verify scripts with && (e.g. check && knip). List leaf scripts in one --parallel orchestrator, or use <group>:* when a step has multiple paths.

Use && only inside a single step when the shell must run multiple commands as one action (e.g. build:netlify, generate-types).

Existing scripts that break the colon rule

These predate the rule and are not run through <group>:*: build:netlify, build:local, generate-types:*, updatePackages:*, export:steckbriefe, trassenscout:*, generate:map-images, bleach:*. Do not add more of this kind. Renaming them changes Netlify config and the Trassenscout sync workflow, so do it in a dedicated change.

Related Skills

View on GitHub
GitHub Stars0
CategoryDevelopment
UpdatedNaNy ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low