New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Server Standards

by sqing33 in sqing33/PTNexus

server 修改强制工作流与规范（先读结构文档定位；新文件按分层落目录；业务日志用 logx；导出函数/Handler/Service/Repo 写中文注释；交付自检清单）。

No licenceAuto-check passed

Install Server Standards

skills CLI
$ npx skills add sqing33/PTNexus --skill server-standards -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sqing33/PTNexus server-standards --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sqing33/PTNexus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/server-standards .claude/skills/server-standards && rm -rf skills-src

Use ~/.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/

Facts

Skill name
server-standards
GitHub stars
151
Token cost
~1.3k tokens
SKILL.md length
302 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
None found

At a glance

server 修改强制工作流与规范（先读结构文档定位；新文件按分层落目录；业务日志用 logx；导出函数/Handler/Service/Repo 写中文注释；交付自检清单）。

  • Works in 8 steps: 目标 → 触发范围（何时必须启用） → 强制工作流（先结构，后定位） → …
  • SKILL.md covers 1. 目标, 2. 触发范围（何时必须启用）, 3. 强制工作流（先结构，后定位） and 4. 目录分层与依赖方向（硬性约束）, plus 4 more sections
  • Calls go

What it does

Server Standards is an agent skill from sqing33/PTNexus. server 修改强制工作流与规范（先读结构文档定位；新文件按分层落目录；业务日志用 logx；导出函数/Handler/Service/Repo 写中文注释；交付自检清单）。

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: PT Nexus 是一款支持 Docker 容器化部署、兼容多下载器与多数据库的 PT 种子聚合管理平台，可自动提取标准化种子参数、解析标题组件，智能纠错补充 MediaInfo/截图/简介等内容、适配不同站点发布规范，支持批量转种与自动推送下载器做种，还具备禁转检测、已存在种子智能匹配等机制，搭配本地文件检索、IYUU API…

Example prompts

  • “/server-standards”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. 目标
  2. 触发范围（何时必须启用）
  3. 强制工作流（先结构，后定位）
  4. 目录分层与依赖方向（硬性约束）
  5. 新文件落点与提取器约束（硬性约束）
  6. 函数注释规范（全中文）
  7. 日志打印规范（全中文）
  8. 交付自检清单

What it can do on your machine

Read from SKILL.md and the folder at commit 53eee1f. 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:

    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Server Standards loads about 1.3k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 302 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 302 words (~1,258 tokens).

name
server-standards

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .codex/skills/server-standards of sqing33/PTNexus.

Open the folder on GitHubat commit 53eee1f

Compare with similar skills

Server Standards 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.

Server Standards compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Server Standards this skillsqing33/PTNexus151—~1.3kAutomated safety check: PassNone
Telemetry Standardssupabase/supabase111k—~2kAutomated safety check: PassApache-2.0
Cpp Coding Standardsaffaan-m/ECC275k4 repos~5.6kAutomated safety check: PassMIT
Java Coding Standardsaffaan-m/ECC275k1 repos~2.9kAutomated safety check: PassMIT
Coding Standardsaffaan-m/ECC275k3 repos~2.6kAutomated safety check: PassMIT
Coding Standardsaffaan-m/ECC275k2 repos~2.6kAutomated safety check: PassMIT

Similar skills

  • Telemetry Standards

    supabase/supabase

    Official

    PostHog event tracking standards for Supabase Studio. An agent skill from supabase/supabase.

    111k GitHub stars~2k tokensUpdated today
    Data & AnalyticsAuto-check passed

  • Cpp Coding Standards

    affaan-m/ECC

    C++ coding standards based on the C++ Core Guidelines (isocpp.github.io).

    275k GitHub starsUsed in 4 repos~5.6k tokens
    DevelopmentAuto-check passed

  • Java Coding Standards

    affaan-m/ECC

    Java coding standards for Spring Boot and Quarkus services: naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout.

    275k GitHub starsUsed in 1 repo~2.9k tokens
    DevelopmentAuto-check passed

  • Coding Standards

    affaan-m/ECC

    适用于TypeScript、JavaScript、React和Node.js开发的通用编码标准、最佳实践和模式. An agent skill from affaan-m/ECC.

    275k GitHub starsUsed in 3 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Coding Standards

    affaan-m/ECC

    TypeScript、JavaScript、React、Node.js開発のための汎用コーディング標準、ベストプラクティス、パターン。

    275k GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Coding Standards

    affaan-m/ECC

    TypeScript, JavaScript, React, Node.js 개발을 위한 범용 코딩 표준, 모범 사례 및 패턴.

    275k GitHub starsUsed in 2 repos~2.7k tokens
    DevelopmentAuto-check passed

More from sqing33/PTNexus

  • Worktree Lite

    sqing33/PTNexus

    轻量 Git worktree 流程：修改前创建新 worktree、完成后输出审查摘要、明确询问用户是否合并、合并前生成“动作：修改内容”格式提交信息。Use when users want a simpler replacement for parafork or need create-review-merge flow with explicit merge approval.

    151 GitHub stars~691 tokensUpdated 2 mo ago
    Auto-check passed

  • Wsl Win Notify

    sqing33/PTNexus

    Send native Windows notifications from WSL during coding workflows.

    151 GitHub stars~590 tokensUpdated 2 mo ago
    Auto-check passed

  • Commit Message Formatter

    sqing33/PTNexus

    统一 PTNexus 提交标题为“动作：修改内容”格式，并基于当前改动生成可直接使用的 commit message。Use when users ask to write/optimize/format commit messages, summarize branch changes before commit, or enforce repository commit-title…

    151 GitHub stars~384 tokensUpdated 2 mo ago
    Auto-check passed

Questions about Server Standards

What does Server Standards do?

server 修改强制工作流与规范（先读结构文档定位；新文件按分层落目录；业务日志用 logx；导出函数/Handler/Service/Repo 写中文注释；交付自检清单）。. Server Standards is an agent skill from sqing33/PTNexus.

How do I install Server Standards in Claude Code?

Run `npx skills add sqing33/PTNexus --skill server-standards -a claude-code`. Or copy the skill folder (.codex/skills/server-standards in sqing33/PTNexus) into .claude/skills/server-standards in your project. Claude Code loads it when a task matches its description.

How do I install Server Standards in Codex?

Run `npx skills add sqing33/PTNexus --skill server-standards -a codex`. Or copy the skill folder (.codex/skills/server-standards in sqing33/PTNexus) into .agents/skills/server-standards in your project. Codex loads it when a task matches its description.

Can I use Server Standards 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 sqing33/PTNexus --skill server-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/server-standards, .gemini/skills/server-standards, .github/skills/server-standards and .opencode/skills/server-standards in your project.

What does Server Standards need to run?

Going by SKILL.md and its folder, Server Standards needs the command-line tools its instructions call (go).

Does Server Standards 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 Server Standards 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 Server Standards use?

No licence was found for Server Standards or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Server Standards use?

About 1.3k tokens (SKILL.md is roughly 5k 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 Server Standards?

Skills that share tags, products or a category with Server Standards: Telemetry Standards (supabase/supabase, 111k stars), Cpp Coding Standards (affaan-m/ECC, 275k stars), Java Coding Standards (affaan-m/ECC, 275k stars) and Coding Standards (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Server Standards?

sqing33 (a GitHub user) maintains it in sqing33/PTNexus, which has 151 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on July 12, 2026.

Source: sqing33/PTNexus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.