Total 58,637 skills
Showing 12 of 58637 skills
Evidence-based resume authenticity audit and report generation skill. This skill should be proactively used when users request resume verification, resume fraud detection, candidate experience investigation, GitHub/open source contribution analysis, identification of role inflation from contributor to maintainer/core author, verification of Sino-foreign cooperative education or school titles, business indicator checks, sorting out public disputes, or production of HTML/PDF reports from investigation results. This skill breaks down resumes, screenshots, links, posts, code repositories, and official records into atomic claims, distinguishes between facts, contradictions, accusations, and unverifiable information, and generates self-contained evidence reports that do not include doxxing information and do not present unsubstantiated accusations as facts.
Generate "ASU-style" high-density Chinese technical resumes or Xiaohongshu showcase resumes based on users' real experiences: retain real names, schools, companies, departments, projects and verifiable metrics, proactively retrieve official school titles, enhance expression with colored experience bars, background/metrics/responsibility structure, English technical terms, architecture links, Benchmark, module-level Owner, 0→1 and large Scope narratives, and output self-contained HTML, A4 PDF and publishing images. Use this when users mention ASU style, ASU-style resumes, professional term stacking, technical experience packaging, Xiaohongshu resume long images, school titles, Owner/0-1 or require HTML/PDF. Do not fabricate non-existent educational backgrounds, companies, projects, roles, offers, metrics or achievements; exaggeration must be based on verifiable institutional labels, limited modules and real technical chains.
When you want to brainstorm and check available .com domains for a new project — brand naming, aftermarket pricing (HugeDomains / Afternic / Sedo / Dan), USPTO trademark screening, and social handle availability. Built on Laura Roeder's "work backwards from availability, not from a name you fell in love with" methodology. Uses Vercel CLI + whois + Domainr API + Namecheap API + agent-browser for the pieces each tool actually reliably supports (multi-tool ensemble because no single tool covers everything cleanly). 11-step workflow: budget → brainstorm → primary availability check → whois cross-check → Domainr aggregation → Namecheap price → aftermarket sweep (+ liveness probe for parked/dead domains, drop-watch for expiring ones) → bucket → negotiate → NAME research (trademark + socials) → buy. Triggers on "/domain," "find a domain," "check domain availability," "brainstorm a domain," "what .com is available for X," "domain hunt," "name my project," "is X.com available," "aftermarket price on X.com," "trademark check for X."
Version-pinned inventory of the telemetry (spans, metrics, logs, attributes) emitted by OpenTelemetry collector components and SDK instrumentation packages. Use when working with a covered component — what it emits at a given version, or how emission changed across versions — and when upgrading a component or SDK version, to see the telemetry after the change.
Use for growth diagnosis, discovery, retention, onboarding, experiments, LiveOps, and packaging.
Executing a phased plan in rolling waves where each phase runs as one multi-agent workflow harness: the supervisor elaborates the phase into tasks against the real landed code, launches a workflow that implements with TDD and runs mandatory in-harness review plus an adversarial contrarian pass (and researchers when the phase hits an unknown) before returning verified work, then reviews it, checkpoints with the user, and rolls to the next phase. Use when each wave should be a reviewed multi-agent harness, not a lone subagent. Skip when one supervised subagent per wave suffices (ring:executing-plans) or the full gated cycle is wanted (ring:running-dev-cycle).
Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted burden of proof. Use for pre-public or post-pivot cleanup. Skip for current diff review (use ring:reviewing-code).
286K words of color science applied to UI/UX design. Covers OKLCH/OKLAB color spaces, palette generation, accessibility contrast ratios, color naming, pigment mixing, and historical color theory. By meodai, creator of color-names.
One-time setup that maps the codebase and gathers user-provided product context to write a root PROJECT.md overview of what the project is, who it serves, how it is structured, and how it runs. Use when the user invokes $setup-project-md, says "setup project md", "create PROJECT.md", or asks for a complete project overview document at the repo root.
Running the backend dev cycle: implements every task in a rolling-wave plan.md (ring:writing-plans format) for a Go/TS service, driving specialist agents through Gate 0 implementation/TDD, Gate 8 parallel review, and Gate 9 validation per epic, elaborating later phases at each phase boundary. Use when starting or resuming a gated backend dev cycle with a plan.md (legacy tasks.md only for cycles already in flight; new cycles need the canonical plan format). Skip for frontend (use ring:running-dev-cycle-frontend) or docs-only work.
Manage Symfony configuration with .env files, parameters, secrets vault, and environment-specific settings
Write functional tests for Symfony controllers and HTTP endpoints using WebTestCase, getContainer, loginUser, and DAMA rollback