Minimizing Ty Ecosystem Changes
astral-sh/ruff
A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…
A skill your agent uses when deciding where IPTVnator code belongs, creating or moving Nx projects, changing scoped aliases or tags, editing lint targets, or validating module boundaries.
Install Iptvnator Nx Architecture
$ npx skills add 4gray/iptvnator --skill iptvnator-nx-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install 4gray/iptvnator iptvnator-nx-architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/4gray/iptvnator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/iptvnator-nx-architecture .claude/skills/iptvnator-nx-architecture && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "iptvnator-nx-architecture" agent skill from https://github.com/4gray/iptvnator/tree/master/.codex/skills/iptvnator-nx-architecture into .claude/skills/iptvnator-nx-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iptvnator-nx-architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/4gray/iptvnator/tree/master/.codex/skills/iptvnator-nx-architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add 4gray/iptvnator --skill iptvnator-nx-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install 4gray/iptvnator iptvnator-nx-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/4gray/iptvnator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/iptvnator-nx-architecture .agents/skills/iptvnator-nx-architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "iptvnator-nx-architecture" agent skill from https://github.com/4gray/iptvnator/tree/master/.codex/skills/iptvnator-nx-architecture into .agents/skills/iptvnator-nx-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iptvnator-nx-architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add 4gray/iptvnator --skill iptvnator-nx-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install 4gray/iptvnator iptvnator-nx-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/4gray/iptvnator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/iptvnator-nx-architecture .cursor/skills/iptvnator-nx-architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "iptvnator-nx-architecture" agent skill from https://github.com/4gray/iptvnator/tree/master/.codex/skills/iptvnator-nx-architecture into .cursor/skills/iptvnator-nx-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iptvnator-nx-architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/4gray/iptvnator.git --path .codex/skills/iptvnator-nx-architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add 4gray/iptvnator --skill iptvnator-nx-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install 4gray/iptvnator iptvnator-nx-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/4gray/iptvnator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/iptvnator-nx-architecture .gemini/skills/iptvnator-nx-architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "iptvnator-nx-architecture" agent skill from https://github.com/4gray/iptvnator/tree/master/.codex/skills/iptvnator-nx-architecture into .gemini/skills/iptvnator-nx-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iptvnator-nx-architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install 4gray/iptvnator iptvnator-nx-architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add 4gray/iptvnator --skill iptvnator-nx-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/4gray/iptvnator.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/iptvnator-nx-architecture .github/skills/iptvnator-nx-architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "iptvnator-nx-architecture" agent skill from https://github.com/4gray/iptvnator/tree/master/.codex/skills/iptvnator-nx-architecture into .github/skills/iptvnator-nx-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iptvnator-nx-architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add 4gray/iptvnator --skill iptvnator-nx-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install 4gray/iptvnator iptvnator-nx-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/4gray/iptvnator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/iptvnator-nx-architecture .opencode/skills/iptvnator-nx-architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "iptvnator-nx-architecture" agent skill from https://github.com/4gray/iptvnator/tree/master/.codex/skills/iptvnator-nx-architecture into .opencode/skills/iptvnator-nx-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iptvnator-nx-architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
iptvnator-nx-architecture- GitHub stars
- 7.3k
- Token cost
- ~828 tokens
- SKILL.md length
- 313 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding where IPTVnator code belongs, creating or moving Nx projects, changing scoped aliases or tags, editing lint targets, or validating module boundaries.
- Deciding where IPTVnator code belongs
- SKILL.md covers Discover Before Deciding, Place Code by Ownership, Preserve Boundaries and Validate the Change
- Calls pnpm and eslint
- Moving Nx projects
What it does
Iptvnator Nx Architecture is an agent skill from 4gray/iptvnator. Use when deciding where IPTVnator code belongs, creating or moving Nx projects, changing scoped aliases or tags, editing lint targets, or validating module boundaries.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting. The repository describes itself as: :tv: Cross-platform IPTV player application with multiple features, such as support of m3u and m3u8 playlists, favorites, TV guide, TV archive/catchup and more. The licence is MIT.
When your agent uses it
- Deciding where IPTVnator code belongs
- Moving Nx projects
- Changing scoped aliases
- Editing lint targets
Example prompts
- “/iptvnator-nx-architecture”
What it can do on your machine
Read from SKILL.md and the folder at commit 015ea20. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpmeslint
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Iptvnator Nx Architecture loads about 828 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 313 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from 4gray/iptvnator at commit 015ea20, republished under its MIT licence (© 4gray). 313 words, ~828 tokens.
Download SKILL.mdSave it as
.claude/skills/iptvnator-nx-architecture/SKILL.md (or your agent's skills folder).- name
- iptvnator-nx-architecture
- description
- Use when deciding where IPTVnator code belongs, creating or moving Nx projects, changing scoped aliases or tags, editing lint targets, or validating module boundaries.
IPTVnator Nx Architecture
Discover Before Deciding
In a fresh worktree, install first:
pnpm install --frozen-lockfile
pnpm nx show projects
pnpm nx show project <name>
pnpm nx show projects --withTarget test
pnpm nx show projects --withTarget e2eDiscovery is authoritative. The current app groups are web,
electron-backend, web-backend, remote-control-web, website, web-e2e,
electron-backend-e2e, stalker-mock-server, and xtream-mock-server. Current
tool projects are eslint-tools, packaging, release-tools, and
repository-skills.
Place Code by Ownership
apps/: runtime, development, E2E, and mock-server applications.tools/: repository automation; tag its projectsscope:tools.libs/: domain libraries.type:feature: route and screen orchestration.type:ui: reusable visual components.type:data-access: injectable state, API, persistence, or orchestration.type:util: the destination for new pure helpers and contracts only.
Provider-neutral collection services that coordinate persistence belong in
libs/portal/shared/data-access; pure collection helpers belong in
libs/portal/shared/util; reusable views belong in
libs/portal/shared/ui. Existing injectable/stateful services under a util
path are legacy debt, not placement precedent.
Preserve Boundaries
Every project keeps one scope:*, domain:*, and type:* tag. Enforced type
directions are:
| Source | Allowed dependencies |
|---|---|
| app, E2E, dev-app | feature, UI, data-access, util |
| website | UI, util |
| feature | feature, UI, data-access, util |
| UI | UI, data-access, util |
| data-access | data-access, util |
| util | util |
Domain constraints are additive. Never weaken either constraint to solve a
placement problem. Preserve the documented workspace-shell-util path/tag
exception: its injectable services require type:data-access so app routes can
eagerly import them without loading the lazy shell feature.
Use aliases from tsconfig.base.json and public src/index.ts barrels. Do not
add legacy bare aliases or deep imports. For a buildable library that has a
local package.json, its package name must match its scoped alias.
Validate the Change
Production TypeScript targets under 300 lines; 400 is the hard limit. Tests are
limited to 1200. The legacy baseline may only shrink. See
tools/eslint/max-lines-config.mjs and regenerate after a split with
tools/eslint/generate-max-lines-baseline.mjs; never add a new baseline entry.
Quote recursive globs in command-based lint targets, for example
eslint "apps/<project>/**/*.ts", then compare coverage with
find apps/<project> -name '*.ts' | wc -l.
Discover targets, then run affected lint/test/build targets and the closest
available E2E target; do not invent targets. Canonical guidance:
docs/architecture/nx-workspace-boundaries.md.
© 4gray, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .codex/skills/iptvnator-nx-architecture of 4gray/iptvnator.
Open the folder on GitHubat commit 015ea20
Compare with similar skills
Iptvnator Nx Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Iptvnator Nx Architecture this skill4gray/iptvnator | 7.3k | — | ~828 | Automated safety check: Pass | MIT | |
| Minimizing Ty Ecosystem Changesastral-sh/ruff | 50k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.4k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Babysit PR To Pass CIsgl-project/sglang | 37k | 2 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Summarise Ecosystem Resultsastral-sh/ruff | 50k | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Babysit PR To Pass CI
sgl-project/sglang
Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
- Official
Summarise Ecosystem Results
astral-sh/ruff
A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…
Go Pedantry
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
More from 4gray/iptvnator
All 8 skills in this repoIptvnator Sqlite DB Worker
4gray/iptvnator
A skill your agent uses when changing Electron SQLite IPC, database-worker operations, request-scoped progress or cancellation, worker packaging, or runtime verification of non-EPG database work.
Release Cut
4gray/iptvnator
A skill your agent uses when preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets.
Release Notes
4gray/iptvnator
A skill your agent uses when a change may need a .changes note, the Release note gate fails, or deciding whether type: internal or no-release-note applies.
Iptvnator Theme Style
4gray/iptvnator
A skill your agent uses when changing IPTVnator SCSS tokens, shared layout mixins, portal headers, sidebars, detail views, Electron drag regions, or cross-portal visual consistency.
Iptvnator UI Design
4gray/iptvnator
A skill your agent uses when changing user-visible Angular UI in IPTVnator, especially channel rows or lists, EPG views, settings and playlist surfaces, selection states, shared portal components…
Stalker Portal
4gray/iptvnator
A skill your agent uses when changing Stalker or Ministra routes, stores, catalog or series shapes, playback progress, favorites and recent items, EPG, or remote control.
Related
Categories
Questions about Iptvnator Nx Architecture
What does Iptvnator Nx Architecture do?
A skill your agent uses when deciding where IPTVnator code belongs, creating or moving Nx projects, changing scoped aliases or tags, editing lint targets, or validating module boundaries. Iptvnator Nx Architecture is an agent skill from 4gray/iptvnator. Use when deciding where IPTVnator code belongs, creating or moving Nx projects, changing scoped aliases or tags, editing lint targets, or validating module boundaries.
When should I use Iptvnator Nx Architecture?
Iptvnator Nx Architecture fits situations like: deciding where IPTVnator code belongs; moving Nx projects; changing scoped aliases; editing lint targets.
How do I install Iptvnator Nx Architecture in Claude Code?
Run `npx skills add 4gray/iptvnator --skill iptvnator-nx-architecture -a claude-code`. Or copy the skill folder (.codex/skills/iptvnator-nx-architecture in 4gray/iptvnator) into .claude/skills/iptvnator-nx-architecture in your project. Claude Code loads it when a task matches its description.
How do I install Iptvnator Nx Architecture in Codex?
Run `npx skills add 4gray/iptvnator --skill iptvnator-nx-architecture -a codex`. Or copy the skill folder (.codex/skills/iptvnator-nx-architecture in 4gray/iptvnator) into .agents/skills/iptvnator-nx-architecture in your project. Codex loads it when a task matches its description.
Can I use Iptvnator Nx Architecture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 4gray/iptvnator --skill iptvnator-nx-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/iptvnator-nx-architecture, .gemini/skills/iptvnator-nx-architecture, .github/skills/iptvnator-nx-architecture and .opencode/skills/iptvnator-nx-architecture in your project.
What does Iptvnator Nx Architecture need to run?
Going by SKILL.md and its folder, Iptvnator Nx Architecture needs the command-line tools its instructions call (pnpm and eslint).
Does Iptvnator Nx Architecture access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Iptvnator Nx Architecture safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Iptvnator Nx Architecture use?
Iptvnator Nx Architecture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Iptvnator Nx Architecture use?
About 828 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Iptvnator Nx Architecture?
Skills that share tags, products or a category with Iptvnator Nx Architecture: Minimizing Ty Ecosystem Changes (astral-sh/ruff, 50k stars), Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.4k stars), Babysit PR To Pass CI (sgl-project/sglang, 37k stars) and Rust Best Practices (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Iptvnator Nx Architecture?
4gray (a GitHub user) maintains it in 4gray/iptvnator, which has 7,318 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 10, 2026.
Source: 4gray/iptvnator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.