Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 16891–16920 of 18825 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| anydesignavelikiy/great_ctoAnalyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| archetype-review-baseavelikiy/great_ctoShared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| artifact-retentionavelikiy/great_ctoAfter a build is delivered, delete its intermediate copies and old versions — keep exactly the version that runs and one previous for rollback — and report the space freed as measured by `df`, never `du`. Covers local build output, mobile build caches, container images, release dirs and stale browser-session copies, with a never-delete list (volumes, databases, installed SDKs, simulator runtimes, the rollback version). Use after any release or image build, before heavy builds when free disk is low, and when disk space drops fast ("диск кончается", "почисти старые сборки", "ENOSPC"). Loaded by release-manager, devops. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| brainstormingavelikiy/great_ctoStructured idea generation + multi-LLM debate for the product-owner stage. Diverge (generate genuinely different bets), debate (a 4-persona panel on 4 models argues over 2 rounds), converge (synthesize a recommendation). Used by product-owner before architect; available to architect for design-space exploration. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| build-speedavelikiy/great_ctoMake a slow CI pipeline or build faster by measuring it first — per-step durations, the slowest step, a target — then one change at a time, re-measured the same way. Speed never comes from removing, skipping or weakening a check. Use when a build or CI is slow ("CI долго", "ускорь сборку", "гейт идёт 40 минут", "build takes forever"). Loaded by devops, ci-resolver. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| codex-hostavelikiy/great_ctoRun the great_cto controlled Codex lifecycle with controller-owned writes, verifier evidence, human gates and optional artifact release. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| committed-aestheticavelikiy/great_ctoHow to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick, and it picks the modal option; a committed aesthetic makes it execute one thing precisely, against rules you can check. Use when a design keeps coming out competent and forgettable, when starting a new brand surface with no reference, or when authoring a house style you want executed the same way twice. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| cost-modelavelikiy/great_ctoStandardized cost-estimation framework for great_cto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| crystallizeavelikiy/great_ctoDistils repeating patterns from session logs and lessons.md into draft skill files. Run after ≥10 sessions to extract durable knowledge. Output: draft skills/ files + promotion report. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| decision-evalavelikiy/great_ctoSpawns the decision-scorer agent after architect proposes 2+ variants in an ADR. Produces a weighted scoring table and recommended choice saved to docs/decisions/. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| deploy-landedavelikiy/great_ctoProve a deploy landed — the served revision is the commit you meant, its env is present, and the product does its job — instead of trusting the deploy command's exit code. Also catches server drift before a pull or deploy. Use after any deploy, rollout, restart or server-side fix ("задеплой", "выкати", "проверь на проде", "почему не обновилось"). Loaded by devops, release-manager, l3-support, infra-provisioner. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| discoveryavelikiy/great_ctoStructured pre-design questioning to surface hidden constraints before any architecture decision is locked in. Forces the architect/auditor/reviewer to enumerate what they DON'T know before proposing. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| done-blockedavelikiy/great_ctoReusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| great_ctoavelikiy/great_ctoUse when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| lifecycle-messagingavelikiy/great_ctoEmail/SMS lifecycle and deliverability framework for SMB Product-Builder products that send transactional or lifecycle messages (booking reminders, CRM sequences, receipts, win-back). Codifies provider selection (Resend/Postmark/Twilio/SendGrid), domain auth (SPF/DKIM/DMARC), consent and compliance (TCPA, CAN-SPAM, CASL, quiet hours, double opt-in), suppression-list discipline, and the transactional-vs-marketing split. Applied by integrations-engineer and senior-dev whenever a feature sends messages — so deliverability and consent are designed in, not bolted on after the first spam complaint. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| migration-ready-schemaavelikiy/great_ctoData-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns. Every SMB Product-Builder product must let a customer bring their data from an incumbent (ServiceTitan/Toast/Mindbody/Shopify) — that requires provenance (source_ref) and rollback (import_batch_id) on importable entities, and modelling real-world actors as entities rather than inline fields. Applied by architect when writing the data model in ARCH-{slug}.md, and checked by migration-import-engineer. One cheap rule set prevents the migration↔architecture seam gap from recurring across all 40 products. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| mobile-releaseavelikiy/great_ctoShip an iOS or Android build to testers and stores without reusing a build number or shipping an OTA bundle that crashes on launch. Covers version and build-number policy, code signing done by the project's own tooling, TestFlight / Play internal / Firebase uploads, Maestro on the uploaded build, phased rollout and halt, OTA runtime compatibility, and the store hand-off. Use for any mobile release step ("собери сборку для тестировщиков", "выложи во внутренний трек", "подними номер сборки", "обнови по воздуху", "отправь в стор"). Loaded by release-manager. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| observability-baselineavelikiy/great_ctoScaffold-time observability so a shipped product is not blind in prod from day one — error capture (Sentry), request-id structured logging, and /healthz + /readyz endpoints. stack-baseline pins Sentry but nothing wires it; this is the wiring. Loaded by app-scaffolder (bake into the scaffold), infra-provisioner (prod env + probes), and consumed by l3-support (traces) and devops (deploy gate). | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| opportunity-solution-treeavelikiy/great_ctoBuild an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a PRD for a complex feature space. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| outcome-roadmapavelikiy/great_ctoTransform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| pm-planningavelikiy/great_ctoDecomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| pre-mortemavelikiy/great_ctoImagine the project has already shipped and failed catastrophically — work backwards from the failure to identify the most likely causes BEFORE building. Forces concrete risk identification, not vague "what could go wrong" lists. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| product-economicsavelikiy/great_ctoDoes this product make money at a price someone will pay? Forces contribution margin, a price with a stated basis, and a bottom-up market size — each number labelled measured / assumed / unknown, so a guess can never be read as a calculation. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| prose-styleavelikiy/great_ctoReusable writing-style contract for agent outputs (reports, ARCH docs, verdicts, threat models). Forces direct prose with concrete evidence, no marketing voice, no hedge words. The single most-referenced skill across the pipeline — used by 28 agents. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| quant-validationavelikiy/great_ctoThe methods a financial-ML result has to survive before it is evidence — purged cross-validation with an embargo, triple-barrier labelling, sample uniqueness under overlapping labels, fractional differentiation, meta-labelling, and multiple-testing correction. Written because the invariants were required of quant-researcher and nothing in the project explained how to satisfy them: a rule without a method produces either an invention or a block. Applied whenever a backtest, a feature or a label is being designed or judged. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| reference-lockavelikiy/great_ctoTurn design references into a written lock and a decision ledger before any UI is built, then check the build against the lock. Names where references come from (free sources first), what to keep from the one dominant reference, what to borrow, what to reject, and which choice traces to which source. Use when a design draws on references — a URL, screenshots, a named product, a reference MCP — so the result neither averages them into the safe centre nor drifts from them during implementation. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| secrets-rotationavelikiy/great_ctoWhat to do the moment a secret is exposed — pasted into chat, committed, logged, shown in a transcript or a screenshot. The secret is compromised; only revoking and rotating it helps. Turns it into one tracked task with an escalation, not a reminder repeated every session. Use when you see a key, token, password or private key anywhere it should not be ("ключ в чате", "токен в логах", "закоммитил .env"). Loaded by security-officer, l3-support, devops. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| signing-preflightavelikiy/great_ctoBefore the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of implementation work in a repo that signs commits ("коммиты не подписаны", "ssh-keygen висит", "gpg failed to sign"). Loaded by senior-dev, devops. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| skeptical-triageavelikiy/great_ctoReusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of ~4 extra LLM turns. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |
| stack-baselineavelikiy/great_ctoThe pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability, with the chosen default + the one sanctioned alternative for each. Applied whenever a new product is scaffolded or a stack choice would otherwise be improvised. Re-deciding the stack every build is the biggest silent time sink; this kills it. | Stars: 117 | Updated | Claude CodeCodex | Unverified | Install |