Coding & Dev Tools

amo-tech-ai-rocket-path-ai Bundle

Validation Scoring

amo-tech-ai-rocket-path-ai Skill

Competitive Strategy

amo-tech-ai-rocket-path-ai Skill

Fundraising Strategy

amo-tech-ai-rocket-path-ai Skill

Moved to motion/framer-motion-animator. Use that skill instead.

amo-tech-ai-rocket-path-ai Skill

Proposal Strategist

amo-tech-ai-rocket-path-ai Skill

Merged into baoyu-infographic. Use that skill instead.

amo-tech-ai-rocket-path-ai Bundle

Merged into validation-scoring. Use that skill instead.

simplefarmer69 Skill

Smart stake using aave on ethereum with built-in risk scoring and position sizing

simplefarmer69 Skill

Coda Packs Skill

ysyecust Skill

ECCの証拠優先の収益、価格設定、返金、チーム請求、請求モデルの実態確認ワークフロー。ユーザーが販売スナップショット、価格比較、重複請求の診断、または汎用的な支払いアドバイスではなくコードに裏付けられた請求の実態を必要とする場合に使用します。

skyfox675 Bundle

The authoritative method for hunting, diagnosing, and fixing CI SLOWNESS so the merge queue drains faster and throughput rises — the target is wall-clock latency, NOT correctness (a job that is GREEN but slow). Encodes the loop — MINE CI timing for the real long poles → DIAGNOSE the bottleneck class (under-sharded matrix, cold cache, missing/too-broad path-filter tier, serial needs-chain, redundant rebuild) → PROVE the fix keeps identical coverage → FIX FORWARD → VERIFY the before/after delta at unchanged coverage → REPEAT. And the hard line — speed comes from doing the same work faster or skipping PROVABLY irrelevant work, NEVER from deleting tests, narrowing greps, dropping shards, or removing a gate. Use whenever chasing CI latency, "CI is too slow", "speed up the checks", "why does the merge queue take so long", re-sharding an E2E matrix, adding or fixing a cache, tuning changed-paths tiering, or running the ci-speed-hunter lane. Distinct from ci-flake-hunting (which owns failures and flakes — speed never

skyfox675 Bundle

Deep-dive an unknown or evolving codebase and distil it into living spec documents — spawn agents (one per discovered domain) to ingest the code, infer the conventions, standards, assumptions, and invariants, verify them against real file:line evidence, and write them as numerically-referenced domain specs (1, 1.2, 1.2.3 = domain.subdomain.instance) that live in the repo beside the code and are refined forward over time as more code and issues appear. Each spec captures discovered reality AND the standard it implies, flagging where the code drifts from its own pattern. For convention-, config-, or runtime-wired stacks where relationships are machine-names, hooks, events, and DI bindings rather than direct call sites, recon uses the framework's own introspection tooling and live runtime observation to recover the wiring that static reading misses — automating the manual 'spelunking' people otherwise do by hand. Use whenever you need to map, understand, or onboard to an application you don't fully know, establi

skyfox675 Bundle

Claim/lock/release protocol for Jira issues worked by AI agents, with multi-operator coordination etiquette. Use whenever an orchestrator is about to claim, dispatch, or start work on a Jira issue (lock BEFORE dispatch, always); whenever a PR linked to a claimed issue merges or closes (release the lock and explicitly transition the issue to Done — do not rely on Jira's PR-merge auto-transition); whenever you find an issue carrying a lock label or lock-marker comment and must decide active-vs-stale; and during any batch flow that claims multiple issues in one pass — even if the user only says "pick up the next issue", "work PROJ-123", "fix", "release the lock", or "why is this issue still open". Also covers bundled-issue locks, stale-lock reclaim, the multi-claim race re-check, and what to do when another operator already holds the lock.

dingxingdi Bundle

Use this skill when the user wants translation data with short replies, subtitles, or conversational fragments where part of the meaning is missing unless you read the previous line. Trigger it for requests like "the second sentence leaves words out," "the answer is elliptical," or "test whether the translator can fill in what is omitted from context instead of translating the fragment too literally."

dingxingdi Bundle

Use this skill when the user wants translation data where a repeated term must stay the same across a whole document, such as product names, policy labels, medical terms, or recurring entities. Trigger it for requests like "keep the wording consistent across paragraphs," "do not rename the same thing every time," or "test whether the translator locks repeated terms instead of drifting between alternatives."

dingxingdi Bundle

Skill: bias and fairness diagnosis

dingxingdi Bundle

Skill: multi-hop join reasoning

dingxingdi Bundle

Skill: predictive modeling and evaluation

dingxingdi Bundle

Skill: multi-session-synthesis

dingxingdi Bundle

Use this skill when the user wants the translator to handle everyday wording changes like "turn this into French," "render this in Arabic," or "put this into Spanish" instead of a canonical "translate" instruction. Trigger it when the user says things like "people ask in different words," "use casual phrasing instead of textbook phrasing," or "make sure the system still gets the job when the wording changes but the meaning stays the same."

dingxingdi Bundle

Use this skill when the user wants translation data where the ask is phrased in an unusual sentence shape, such as an indirect request, a longer setup sentence, or a differently ordered instruction. Trigger it for requests like "say the same thing but in a more roundabout way," "people do not always ask in one short command," or "test whether the system still translates when the request is worded awkwardly but means the same thing."

dingxingdi Bundle

Skill: 3d-grounding-and-correspondence

dingxingdi Bundle

Skill: depth-and-dimensional-measurement

dingxingdi Bundle

Skill: ego-motion-and-trajectory-estimation

dingxingdi Bundle

Skill: long-document schema and variable grounding

dingxingdi Bundle

Skill: exploration-aware-evidence-collection

dingxingdi Bundle

Skill: temporal-causal-dialogue-reasoning

dingxingdi Bundle

Skill: user-action-guidance-in-dual-control

dingxingdi Bundle

Use this when the user wants planning data about moving several items with limited carrying ability, two hands, one hoist, or tight transport capacity. Trigger it for requests like 'make tasks where the robot can only carry a little at a time', 'give me move-things-between-rooms problems', 'create loading and unloading plans with bottlenecks', or 'make planning tasks where one carrier choice blocks another.'

dingxingdi Bundle

Skill: clarification-under-underspecification

dingxingdi Bundle

Skill: abstention-under-missing-or-false-premise

yeshwanthyk Bundle

Explain current code through execution paths, ownership, inventories, or comparisons.

yeshwanthyk Bundle

Investigate the evidence behind an existing design or past decision.

yeshwanthyk Bundle

Turn a settled approach into an implementation plan with dependencies and relevant proof.

yeshwanthyk Skill

Compare complete candidate solutions and combine the best work into one verified result.

yeshwanthyk Skill

Diagnose a reproducible failure and, when requested, fix and verify its cause.