[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77STR2CCSVXSSA3E7Y7CCBF":3,"skill-same:01M77STR2CCSVXSSA3E7Y7CCBF":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77STR2CCSVXSSA3E7Y7CCBF","lvtd-skills-router",null,"Use when the user is unsure which LVTD skill fits their problem, asks what skill to use, describes a cross-domain workflow, or needs help choosing between Django, Rust, SEO, B2B sales, writing, product, library, or template skills.","ConcertoNotes\u002Fcodex-plugins","ConcertoNotes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249301288?v=4","01M77NJ0BK2KN5YW0D8RHD99TB","01M77NJ0CCEDPATAY3JTXEWNK5",0,"MIT","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Flvtd-skills-router\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lvtd-skills-router\ndescription: Use when the user is unsure which LVTD skill fits their problem, asks what skill to use, describes a cross-domain workflow, or needs help choosing between Django, Rust, SEO, B2B sales, writing, product, library, or template skills.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Skills Router\n  category: Productivity\n  tags: skills,router,workflow,agents\n---\n\n# LVTD Skills Router\n\nUse this skill to choose the smallest useful set of LVTD skills for the user's\nproblem. All skills in this catalog can be model-invoked; this router exists to\nreduce selection friction, not to create a separate manual-only command layer.\n\n## Routing Workflow\n\n1. Identify the user's domain, desired outcome, and whether they are asking for\n   advice, implementation, review, or troubleshooting.\n2. Choose one primary skill. Add secondary skills only when they clearly cover a\n   separate concern in the same workflow.\n3. If the user asked which skill to use, answer with the recommendation and why.\n4. If the user asked for work to be done and the matching skill is available,\n   continue by using that skill's workflow.\n5. If the matching skill is not installed in the current client, name the skill\n   and the marketplace plugin that contains it.\n\n## Skill Map\n\nUse these defaults when the user's request is ambiguous:\n\n- `django-htmx`: HTMX interactions, partial templates, request branching,\n  swaps, triggers, redirects, and server-rendered Django UI.\n- `alpinejs-django`: Alpine.js behavior in Django templates, especially local\n  UI state around HTMX swaps.\n- `django-q2`: Django Q2 tasks, schedules, qcluster workers, Redis broker\n  setup, and background job debugging.\n- `django-test-profiling`: finding the slowest Django tests and runtime\n  bottlenecks before optimizing.\n- `django-test-performance`: improving slow Django test suites after the\n  bottlenecks are known or likely.\n- `django-test-data`: cleaning up factories, fixtures, setup methods, and\n  database-heavy test data.\n- `django-test-parallelization`: enabling or debugging Django parallel test\n  execution, pytest-xdist, and shared-resource isolation.\n- `django-ci-test-optimization`: tuning Django test jobs in CI, including\n  caching, splitting, and command design.\n- `django-targeted-mocking`: replacing external services, settings, time,\n  stdin\u002Fstdout, or HTTP calls in Django tests without broad fragile mocks.\n- `fastmcp-django`: FastMCP servers inside Django apps, including ASGI mounting,\n  ORM access, auth, and Streamable HTTP deployment.\n- `rust-api-test-harness`: Rust HTTP API test harnesses, black-box integration\n  tests, random-port app startup, real database isolation, and CI cargo checks.\n- `rust-sqlx-postgres-service`: SQLx migrations, compile-time checked queries,\n  pool injection, transactions, and Postgres integration tests.\n- `rust-domain-boundaries`: newtypes, parse-don't-validate constructors,\n  request DTO boundaries, and property tests.\n- `rust-error-observability`: typed errors, HTTP adapters, tracing spans,\n  redaction, and async failure diagnosis.\n- `rust-service-security`: login, password hashing, sessions, route protection,\n  and authentication middleware.\n- `rust-idempotent-workflows`: retry-safe workflows, duplicate requests,\n  queues, side effects, concurrency, and idempotency keys.\n- `rust-deployable-service`: Docker, runtime config, secrets, health checks,\n  SQLx offline builds, and production startup validation.\n- `game-geometry-representation-choice`: choosing between meshes, SDFs,\n  voxels, splines, parametric surfaces, fields, and hybrid game-geometry\n  workflows before implementation.\n- `game-spatial-queries`: raycasts, picking, collision predicates,\n  point-in-triangle checks, barycentric constraints, signed distances, and\n  geometry query edge cases.\n- `game-transform-systems`: coordinate spaces, local\u002Fworld\u002Fview\u002Fprojection\n  transforms, homogeneous coordinates, camera constraints, parent-child\n  transforms, and inverse transforms.\n- `game-vector-math-primitives`: dot, cross, and triple products for game\n  rendering, collision, orientation, normals, projections, signed areas, and\n  signed volumes.\n- `game-smooth-curves-and-motion`: splines, Bezier curves, interpolation,\n  derivative continuity, path parameterization, camera rails, waypoint paths,\n  and smooth game motion.\n- `game-sdf-and-field-modeling`: SDF primitives, implicit functions, scalar\n  fields, vector fields, deformation fields, procedural volumes, and field\n  composition.\n- `game-mesh-voxel-conversion`: mesh, SDF, voxel, image, contour, and smooth\n  curve conversions, including mesh repair, contouring, voxel morphology, and\n  attribute preservation.\n- `cookiecutter`: Cookiecutter templates, Jinja rendering, hooks, options,\n  generated project validation, and template cleanup.\n- `seo-opportunity-research`: finding organic growth opportunities from\n  customer demand, search behavior, communities, and competitive gaps.\n- `seo-persona-intent-mapping`: mapping personas, search intent, funnel stage,\n  formats, CTAs, and localization needs into SEO plans.\n- `product-led-seo-strategy`: turning product value, page architecture,\n  taxonomy, and scalable experiences into a product-led SEO strategy.\n- `seo-roadmap-prioritization`: scoring SEO initiatives, sequencing roadmap\n  work, and framing cross-functional SEO asks.\n- `technical-seo-triage`: diagnosing traffic drops, indexing failures,\n  canonicals, redirects, crawlability, and migration risk.\n- `link-building-strategy`: designing sustainable link-building campaigns\n  around business outcomes, assets, publisher ecosystems, metrics, and scope.\n- `linkable-asset-planning`: planning or auditing link-worthy assets from\n  market pains, existing strengths, competitor evidence, and linker audiences.\n- `link-prospecting-research`: researching link opportunity types, queries,\n  competitor backlink angles, list sources, and autocomplete seed expansions.\n- `link-prospect-qualification`: scoring link prospects for relevance, trust,\n  editorial quality, authority, outreach fit, spam risk, and asset readiness.\n- `link-outreach-acquisition`: drafting and operating link outreach with\n  personalization, subject lines, response handling, tracking, and guardrails.\n- `broken-link-building`: finding dead-resource opportunities, qualifying\n  dead backlinks, preparing replacement outreach, and salvaging old owned URLs.\n- `guest-post-placement`: planning citation-justified guest post placements,\n  publisher quality checks, pitch titles, and placement tracking.\n- `local-sponsorship-link-building`: planning local sponsorship campaigns for\n  local visibility, relationships, fulfillment, measurement, and links.\n- `book-toc-lab`: planning or restructuring useful nonfiction books around a\n  promise, scope, reader outcome, and takeaway-first table of contents.\n- `reader-experience-edit`: revising practical nonfiction for usefulness,\n  pacing, front-loaded insight, and beta-readiness.\n- `beta-reader-feedback`: planning beta rounds and turning reader feedback into\n  manuscript revisions.\n- `book-seed-marketing`: choosing first-reader channels and seed marketing for\n  useful nonfiction books.\n- `book-sales-optimization`: improving book product pages, retailer funnels,\n  pricing, formats, reviews, and post-launch sales.\n- `self-publishing-production`: final production sequencing for editing,\n  proofreading, layout, cover, print-on-demand, ISBNs, and launch readiness.\n- `customer-discovery-conversations`: planning or auditing customer discovery\n  conversations so they produce concrete evidence instead of compliments,\n  opinions, hypotheticals, or feature-request noise.\n- `customer-commitment-validation`: evaluating whether customer, sales,\n  investor, partner, or product meetings created real commitment and\n  advancement.\n- `customer-segment-slicing`: narrowing broad markets, audiences, or personas\n  into specific, reachable who-where customer segments.\n- `customer-conversation-access`: finding and framing customer conversations\n  through warm intros, communities, casual chats, events, advisors, landing-page\n  replies, or meeting requests.\n- `customer-learning-notes`: synthesizing raw customer notes, transcripts, call\n  summaries, or CRM snippets into shared team learning and next questions.\n- `b2b-sales-constraint-diagnosis`: diagnosing the one sales bottleneck limiting\n  current pipeline or revenue: reach, resonance, timing, or trust.\n- `b2b-reach-engineering`: building named-account reach systems, target buyer\n  lists, controlled delivery channels, and first-touch saturation plans.\n- `b2b-resonance-audit`: auditing and rewriting B2B messaging around buyer\n  pain, concrete outcome, and mechanism so the right buyers remember it.\n- `b2b-timing-engine`: designing 4-6 week buyer-presence cadences so known\n  buyers remember the company when pain becomes urgent.\n- `b2b-trust-engineering`: reducing perceived buying risk with relevant proof,\n  clear next steps, layered familiarity, and confirmatory sales calls.\n- `traction-bullseye`: choosing and focusing startup traction channels.\n- `traction-channel-research`: researching comparable growth paths and channel\n  options before Bullseye ranking.\n- `traction-test-planner`: designing cheap, measurable channel tests and\n  success criteria.\n- `traction-review`: reviewing traction experiment results and deciding whether\n  to double down, iterate, or pivot.\n- `traction-critical-path`: setting traction goals and deciding what not to do.\n- `traction-seo-content`, `traction-email-marketing`,\n  `traction-paid-acquisition`, `traction-events-community`,\n  `traction-partnership-sales`, `traction-pr-playbook`, and\n  `traction-viral-engineering`: channel-specific traction test planning.\n- `make-product-viral`: improving a product, landing page, pricing page, launch\n  page, free tool, or social preview for clarity, memorability, and sharing.\n- `calibredb`: managing Calibre libraries through the `calibredb` CLI.\n\n## Marketplace Plugins\n\n- `router`: `lvtd-skills-router`\n- `django`: Django server-rendered UI, jobs, FastMCP, and test optimization\n  skills.\n- `rust`: Rust API testing, persistence, domain, observability, security,\n  idempotency, and deployment skills.\n- `game-geometry`: game geometry representation choice, spatial queries,\n  transforms, vector primitives, smooth curves, SDFs, fields, mesh and voxel\n  conversion.\n- `seo`: `seo-opportunity-research`, `seo-persona-intent-mapping`,\n  `product-led-seo-strategy`, `seo-roadmap-prioritization`,\n  `technical-seo-triage`, `link-building-strategy`,\n  `linkable-asset-planning`, `link-prospecting-research`,\n  `link-prospect-qualification`, `link-outreach-acquisition`,\n  `broken-link-building`, `guest-post-placement`,\n  `local-sponsorship-link-building`\n- `nonfiction-book-writing`: nonfiction planning, editing, beta feedback,\n  seed marketing, sales optimization, and production skills.\n- `customer-discovery`: customer interviews, segment slicing, access,\n  commitment validation, and notes synthesis.\n- `b2b-sales`: constraint diagnosis, reach engineering, resonance audits,\n  timing engines, and trust engineering for B2B sales.\n- `traction`: startup traction, channel research, test planning, and\n  channel-specific growth skills.\n- `cookiecutter`: `cookiecutter`\n\n`calibredb` and `make-product-viral` may be direct-install skills when they are\nnot present in a generated marketplace plugin.\n\n## Avoid\n\n- Do not load every candidate skill just to browse. Route from the user's\n  current request first.\n- Do not continue routing once a specific skill clearly fits.\n- Do not force a planning\u002Fexecution taxonomy onto the catalog. Pick by domain,\n  outcome, and evidence needed for the current request.\n","# LVTD Skills Router\n\nUse this skill to choose the smallest useful set of LVTD skills for the user's\nproblem. All skills in this catalog can be model-invoked; this router exists to\nreduce selection friction, not to create a separate manual-only command layer.\n\n## Routing Workflow\n\n1. Identify the user's domain, desired outcome, and whether they are asking for\n   advice, implementation, review, or troubleshooting.\n2. Choose one primary skill. Add secondary skills only when they clearly cover a\n   separate concern in the same workflow.\n3. If the user asked which skill to use, answer with the recommendation and why.\n4. If the user asked for work to be done and the matching skill is available,\n   continue by using that skill's workflow.\n5. If the matching skill is not installed in the current client, name the skill\n   and the marketplace plugin that contains it.\n\n## Skill Map\n\nUse these defaults when the user's request is ambiguous:\n\n- `django-htmx`: HTMX interactions, partial templates, request branching,\n  swaps, triggers, redirects, and server-rendered Django UI.\n- `alpinejs-django`: Alpine.js behavior in Django templates, especially local\n  UI state around HTMX swaps.\n- `django-q2`: Django Q2 tasks, schedules, qcluster workers, Redis broker\n  setup, and background job debugging.\n- `django-test-profiling`: finding the slowest Django tests and runtime\n  bottlenecks before optimizing.\n- `django-test-performance`: improving slow Django test suites after the\n  bottlenecks are known or likely.\n- `django-test-data`: cleaning up factories, fixtures, setup methods, and\n  database-heavy test data.\n- `django-test-parallelization`: enabling or debugging Django parallel test\n  execution, pytest-xdist, and shared-resource isolation.\n- `django-ci-test-optimization`: tuning Django test jobs in CI, including\n  caching, splitting, and command design.\n- `django-targeted-mocking`: replacing external services, settings, time,\n  stdin\u002Fstdout, or HTTP calls in Django tests without broad fragile mocks.\n- `fastmcp-django`: FastMCP servers inside Django apps, including ASGI mounting,\n  ORM access, auth, and Streamable HTTP deployment.\n- `rust-api-test-harness`: Rust HTTP API test harnesses, black-box integration\n  tests, random-port app startup, real database isolation, and CI cargo checks.\n- `rust-sqlx-postgres-service`: SQLx migrations, compile-time checked queries,\n  pool injection, transactions, and Postgres integration tests.\n- `rust-domain-boundaries`: newtypes, parse-don't-validate constructors,\n  request DTO boundaries, and property tests.\n- `rust-error-observability`: typed errors, HTTP adapters, tracing spans,\n  redaction, and async failure diagnosis.\n- `rust-service-security`: login, password hashing, sessions, route protection,\n  and authentication middleware.\n- `rust-idempotent-workflows`: retry-safe workflows, duplicate requests,\n  queues, side effects, concurrency, and idempotency keys.\n- `rust-deployable-service`: Docker, runtime config, secrets, health checks,\n  SQLx offline builds, and production startup validation.\n- `game-geometry-representation-choice`: choosing between meshes, SDFs,\n  voxels, splines, parametric surfaces, fields, and hybrid game-geometry\n  workflows before implementation.\n- `game-spatial-queries`: raycasts, picking, collision predicates,\n  point-in-triangle checks, barycentric constraints, signed distances, and\n  geometry query edge cases.\n- `game-transform-systems`: coordinate spaces, local\u002Fworld\u002Fview\u002Fprojection\n  transforms, homogeneous coordinates, camera constraints, parent-child\n  transforms, and inverse transforms.\n- `game-vector-math-primitives`: dot, cross, and triple products for game\n  rendering, collision, orientation, normals, projections, signed areas, and\n  signed volumes.\n- `game-smooth-curves-and-motion`: splines, Bezier curves, interpolation,\n  derivative continuity, path parameterization, camera rails, waypoint paths,\n  and smooth game motion.\n- `game-sdf-and-field-modeling`: SDF primitives, implicit functions, scalar\n  fields, vector fields, deformation fields, procedural volumes, and field\n  composition.\n- `game-mesh-voxel-conversion`: mesh, SDF, voxel, image, contour, and smooth\n  curve conversions, including mesh repair, contouring, voxel morphology, and\n  attribute preservation.\n- `cookiecutter`: Cookiecutter templates, Jinja rendering, hooks, options,\n  generated project validation, and template cleanup.\n- `seo-opportunity-research`: finding organic growth opportunities from\n  customer demand, search behavior, communities, and competitive gaps.\n- `seo-persona-intent-mapping`: mapping personas, search intent, funnel stage,\n  formats, CTAs, and localization needs into SEO plans.\n- `product-led-seo-strategy`: turning product value, page architecture,\n  taxonomy, and scalable experiences into a product-led SEO strategy.\n- `seo-roadmap-prioritization`: scoring SEO initiatives, sequencing roadmap\n  work, and framing cross-functional SEO asks.\n- `technical-seo-triage`: diagnosing traffic drops, indexing failures,\n  canonicals, redirects, crawlability, and migration risk.\n- `link-building-strategy`: designing sustainable link-building campaigns\n  around business outcomes, assets, publisher ecosystems, metrics, and scope.\n- `linkable-asset-planning`: planning or auditing link-worthy assets from\n  market pains, existing strengths, competitor evidence, and linker audiences.\n- `link-prospecting-research`: researching link opportunity types, queries,\n  competitor backlink angles, list sources, and autocomplete seed expansions.\n- `link-prospect-qualification`: scoring link prospects for relevance, trust,\n  editorial quality, authority, outreach fit, spam risk, and asset readiness.\n- `link-outreach-acquisition`: drafting and operating link outreach with\n  personalization, subject lines, response handling, tracking, and guardrails.\n- `broken-link-building`: finding dead-resource opportunities, qualifying\n  dead backlinks, preparing replacement outreach, and salvaging old owned URLs.\n- `guest-post-placement`: planning citation-justified guest post placements,\n  publisher quality checks, pitch titles, and placement tracking.\n- `local-sponsorship-link-building`: planning local sponsorship campaigns for\n  local visibility, relationships, fulfillment, measurement, and links.\n- `book-toc-lab`: planning or restructuring useful nonfiction books around a\n  promise, scope, reader outcome, and takeaway-first table of contents.\n- `reader-experience-edit`: revising practical nonfiction for usefulness,\n  pacing, front-loaded insight, and beta-readiness.\n- `beta-reader-feedback`: planning beta rounds and turning reader feedback into\n  manuscript revisions.\n- `book-seed-marketing`: choosing first-reader channels and seed marketing for\n  useful nonfiction books.\n- `book-sales-optimization`: improving book product pages, retailer funnels,\n  pricing, formats, reviews, and post-launch sales.\n- `self-publishing-production`: final production sequencing for editing,\n  proofreading, layout, cover, print-on-demand, ISBNs, and launch readiness.\n- `customer-discovery-conversations`: planning or auditing customer discovery\n  conversations so they produce concrete evidence instead of compliments,\n  opinions, hypotheticals, or feature-request noise.\n- `customer-commitment-validation`: evaluating whether customer, sales,\n  investor, partner, or product meetings created real commitment and\n  advancement.\n- `customer-segment-slicing`: narrowing broad markets, audiences, or personas\n  into specific, reachable who-where customer segments.\n- `customer-conversation-access`: finding and framing customer conversations\n  through warm intros, communities, casual chats, events, advisors, landing-page\n  replies, or meeting requests.\n- `customer-learning-notes`: synthesizing raw customer notes, transcripts, call\n  summaries, or CRM snippets into shared team learning and next questions.\n- `b2b-sales-constraint-diagnosis`: diagnosing the one sales bottleneck limiting\n  current pipeline or revenue: reach, resonance, timing, or trust.\n- `b2b-reach-engineering`: building named-account reach systems, target buyer\n  lists, controlled delivery channels, and first-touch saturation plans.\n- `b2b-resonance-audit`: auditing and rewriting B2B messaging around buyer\n  pain, concrete outcome, and mechanism so the right buyers remember it.\n- `b2b-timing-engine`: designing 4-6 week buyer-presence cadences so known\n  buyers remember the company when pain becomes urgent.\n- `b2b-trust-engineering`: reducing perceived buying risk with relevant proof,\n  clear next steps, layered familiarity, and confirmatory sales calls.\n- `traction-bullseye`: choosing and focusing startup traction channels.\n- `traction-channel-research`: researching comparable growth paths and channel\n  options before Bullseye ranking.\n- `traction-test-planner`: designing cheap, measurable channel tests and\n  success criteria.\n- `traction-review`: reviewing traction experiment results and deciding whether\n  to double down, iterate, or pivot.\n- `traction-critical-path`: setting traction goals and deciding what not to do.\n- `traction-seo-content`, `traction-email-marketing`,\n  `traction-paid-acquisition`, `traction-events-community`,\n  `traction-partnership-sales`, `traction-pr-playbook`, and\n  `traction-viral-engineering`: channel-specific traction test planning.\n- `make-product-viral`: improving a product, landing page, pricing page, launch\n  page, free tool, or social preview for clarity, memorability, and sharing.\n- `calibredb`: managing Calibre libraries through the `calibredb` CLI.\n\n## Marketplace Plugins\n\n- `router`: `lvtd-skills-router`\n- `django`: Django server-rendered UI, jobs, FastMCP, and test optimization\n  skills.\n- `rust`: Rust API testing, persistence, domain, observability, security,\n  idempotency, and deployment skills.\n- `game-geometry`: game geometry representation choice, spatial queries,\n  transforms, vector primitives, smooth curves, SDFs, fields, mesh and voxel\n  conversion.\n- `seo`: `seo-opportunity-research`, `seo-persona-intent-mapping`,\n  `product-led-seo-strategy`, `seo-roadmap-prioritization`,\n  `technical-seo-triage`, `link-building-strategy`,\n  `linkable-asset-planning`, `link-prospecting-research`,\n  `link-prospect-qualification`, `link-outreach-acquisition`,\n  `broken-link-building`, `guest-post-placement`,\n  `local-sponsorship-link-building`\n- `nonfiction-book-writing`: nonfiction planning, editing, beta feedback,\n  seed marketing, sales optimization, and production skills.\n- `customer-discovery`: customer interviews, segment slicing, access,\n  commitment validation, and notes synthesis.\n- `b2b-sales`: constraint diagnosis, reach engineering, resonance audits,\n  timing engines, and trust engineering for B2B sales.\n- `traction`: startup traction, channel research, test planning, and\n  channel-specific growth skills.\n- `cookiecutter`: `cookiecutter`\n\n`calibredb` and `make-product-viral` may be direct-install skills when they are\nnot present in a generated marketplace plugin.\n\n## Avoid\n\n- Do not load every candidate skill just to browse. Route from the user's\n  current request first.\n- Do not continue routing once a specific skill clearly fits.\n- Do not force a planning\u002Fexecution taxonomy onto the catalog. Pick by domain,\n  outcome, and evidence needed for the current request.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":28},{"tags":24,"version":25,"category":26,"displayName":27},"skills,router,workflow,agents","0.1.0","Productivity","Skills Router","Codex, Claude Code, and other Agent Skills-compatible clients.","main","9ba3c9fadff1092395837bf1502e1b8a7f98b1e1","plugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Flvtd-skills-router","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FConcertoNotes","2026-06-26 10:13:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ConcertoNotes\u002Fcodex-plugins --skill lvtd-skills-router",{"tool":41,"command":42},"bunx","bunx skills add ConcertoNotes\u002Fcodex-plugins --skill lvtd-skills-router",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ConcertoNotes\u002Fcodex-plugins --skill lvtd-skills-router","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Flvtd-skills-router\u002FSKILL.md",true,[],[50,59,66,74,81,88],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":54,"licenseFileUrl":55,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M77YB7WW36DS9AERTWP673E0","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M77Y7AA8N45G6NM0WJSS2W9C","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":54,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M77Y2W5H5YGSW7MYWEJ8HYXD","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M77Y06GV1DAME7PN9KBFHWRX","render-workflows","Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M77Y01A6RJA8VYT7CZ2TVETF","render-web-services","Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M77XZW1AZ6B6NZTWWFVY72T3","render-static-sites","Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React\u002FVue\u002FHugo\u002FGatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]