document-skills

Plugin document-skills from marketplace buyoung-agent-skills in buYoung/skills. Commands read from the repo's manifest — 18 days ago.

Skills (26)

• agents-md-generator

  Analyze repository structure and generate or update standardized AGENTS.md files that serve as contributor guides for AI agents. Supports both single-repo and monorepo structures. Measures LOC to determine character limits and produces structured documents covering overview, optional ownership maps,

• biz-opportunity-scout

  Identify and validate profitable business opportunities by analyzing market size (TAM/SAM/SOM), unit economics, competitive landscape, and PMF indicators. Generates comprehensive HTML reports with opportunity scorecards.

• clear-writing

  Apply ISO 24495-1 to create text that helps readers easily find, understand, and use the information they need. Use this skill only to write, revise, or review practical documents that convey information, explain procedures, or support decision-making, and provide only the requested output.

• code-review

  Review Git changes for concrete defects and evidence-backed maintainability concerns. Use for code review of commits, ranges, staged changes, uncommitted changes, or selected files. With no target, review all staged, unstaged, and untracked changes; ask for a target if none exist. Trace behavior in

• code-security-audit

  Performs OWASP-based code security audits on any codebase. Analyzes source code against ASVS 5.0.0 verification requirements, API Security Top 10 2023 risk patterns, OWASP CheatSheet secure coding practices, and WSTG testing methodologies. Input is a codebase to review; output is a detailed Markdown

• delegated-review-loop

  Run a delegated build-review-improve loop when the user explicitly invokes this skill or explicitly asks to have sub-agents build and iteratively review the work. A worker sub-agent produces the artifact (with an optional scout sub-agent gathering context first), a task-matched panel of independent

• document-writing

  Create, update, rewrite, review, fact-check, or normalize durable human-readable documents. Use for software project READMEs and usage documentation, explanatory overviews, action guides, references or specifications, proposals, analysis reports, policies, troubleshooting runbooks, records or meetin

• iterative-self-review

  Use only when the user explicitly invokes this skill.

• jetbrains-plugin-development

  IntelliJ Platform plugin development for JetBrains IDEs. Use when writing, debugging, or migrating a JetBrains plugin — `plugin.xml`, services, actions, PSI/VFS/Document, EDT/BGT threading and Read/Write actions, Kotlin coroutines on the IDE platform, custom languages (Grammar-Kit, JFlex, lexer/pars

• jetbrains-vmoptions

  Diagnose and tune JetBrains IDE VM options against the IDE's actual boot runtime, including bundled or custom JetBrains Runtime (JBR) 17, 21, and 25. Use whenever a user asks about JetBrains IDE performance, freezes, startup or indexing speed, memory pressure, garbage collection, heap sizing, `.vmop

• kysely-converter

  Convert raw SQL into type-safe Kysely TypeScript, write Kysely queries from requirements without source SQL, modify or refactor existing Kysely code, and diagnose Kysely type errors. Use for SELECT, INSERT, UPDATE, DELETE, joins, CTEs, expressions, and window functions with version-aware SQL dialect

• linear-issue-creator

  Create structured Linear issues (main + sub-issues) with project linking, title prefix, and labeling. Supports two workflows: Generic (code tasks) and PRD Pipeline (제품 요구사항 정의서). PRD Pipeline applies content-strategy, content-production, content-humanizer, copy-editing principles to produce high-qua

• linear-issue-reviewer

  Review completed Linear sub-issues: cross-validate Done Criteria, code changes, and worker comments to approve, request changes, or ask for clarification. Use when asked to review, validate, or QA done Linear issues.

• linear-issue-worker

  Execute code tasks from Linear sub-issues: resolve dependencies, implement changes, validate Done Criteria, and sync status. Use when asked to work on, implement, or start coding a Linear issue (e.g. PRI-42).

• orchestration

  Use only when the user explicitly invokes this skill.

• pi-package-creator

  Create, extend, repair, validate, test, and package Pi coding-agent packages (pi packages, pi-packages, Pi 패키지) for local, npm, or git distribution. Use whenever a request involves a package.json pi manifest, Pi extensions or custom tools, bundled SKILL.md files, prompt templates, themes, resource d

• acme-orient

  Map a workspace's entry points, relevant directories, and development commands. Use when exploring an unfamiliar project or locating the files involved in a proposed change.

• react-guide

  Use for explaining, designing, implementing, reviewing, refactoring, migrating, or diagnosing React 18/19 applications when React-specific judgment is needed for CSR, SSR, streaming, hydration, structure, APIs, Hooks, state/data, async UI, accessibility, performance, compatibility, or Compiler behav

• release-it

  release-it configuration, setup, troubleshooting, and plugin development. Triggers on .release-it.* config files, release-it CLI or programmatic usage, version bumping, changelog generation, npm publishing, GitHub/GitLab releases, git tagging, hooks lifecycle, pre-release workflows, CI/CD pipelines,

• rust-guide

  Use to explain Rust language characteristics and established practical patterns, and to apply that knowledge in Rust development. Covers ownership, borrowing, lifetimes, traits and API design, collections, memory allocation, error handling, async execution and CPU parallelism, synchronization, modul

• skill-creator

  Create, improve, and evaluate reusable agent skills. Use when the user wants to create a skill, revise its instructions or resources, measure its performance, or improve its triggering description. After a complete draft, run one independent-candidate refinement pass before the existing evaluation a

• system-prompt-creator

  Generate system prompts from user requirements, with application guidance and request-derived evaluation materials. Use when asked to create, design, or draft a system prompt for an LLM bot, assistant, classifier, router, or explicitly requested multi-step pipeline (e.g. "create a system prompt", "시

• task-brief-creator-caveman

  Generate an executable implementation work-plan Markdown at `docs/briefs/` from planning notes or a rough task description, with the plan body written in caveman **full** mode as a register-only transform that preserves every fact, bullet, execution stage, field, and section depth from the normal-mo

• task-brief-creator

  Generate an executable implementation work-plan Markdown at `docs/briefs/` from planning notes or a rough task description. Work brief, task brief, handoff brief, implementation ticket, and task spec remain trigger aliases. Nine required sections are keyed to Conventional Commits types so coding age

• typst-creator

  Create, update, review, migrate, or diagnose Typst (.typ) source for documents, reports, papers, and presentations. Use for Typst markup, styling, scripting, math, layout, bibliography, and compiler/export issues. Resolve the compiler and generate source for stable Typst 0.13.0 through 0.15.1, inclu

• vite-guide

  Use for explaining, designing, implementing, reviewing, refactoring, migrating, or diagnosing Vite 7/8 applications when runtime, build, plugin, deployment, performance, or compatibility judgment is needed, including CSR SPA/MPA, backend-embedded clients, and Vite's own SSR development and productio