Loading...
Loading...
Found 919 Skills
Market microstructure analysis via Longbridge Securities — bid-ask spread, order-flow toxicity (large-order pressure), liquidity depth, price impact, and institutional order direction. Covers A-share call-auction analysis and HK block-trade mechanics. Triggers: "盘口分析", "微观结构", "订单流", "大单分析", "买卖价差", "逐笔分析", "买卖盘深度", "挂单墙", "主力动向", "集合竞价", "盤口分析", "微觀結構", "訂單流", "大單分析", "買賣價差", "逐筆分析", "買賣盤深度", "掛單牆", "主力動向", "market microstructure", "order flow", "bid-ask spread", "depth analysis", "large order", "order book imbalance", "price impact", "auction analysis", "institutional order flow".
Use this skill when sending TON or jettons (tokens) to an address or TON DNS domain. It transfers TON, jettons, or other assets to any wallet address, .ton domain, or .t.me domain. Also use when the user wants to pay someone, send funds, transfer tokens, or move assets on the TON blockchain.
Spatial data gridding and interpolation with a machine-learning style API. Process geographic and Cartesian point data onto regular grids. Use when Claude needs to: (1) Grid scattered spatial data onto regular grids, (2) Interpolate point data using splines, linear, or cubic methods, (3) Process geographic coordinates with projections, (4) Reduce large datasets using block averaging, (5) Remove polynomial trends from spatial data, (6) Cross-validate gridding parameters, (7) Create processing pipelines with Chain, (8) Grid vector data like GPS velocities.
This skill should be used when the user asks to draft or structure STR reports, suspicious transaction reports, SAR, suspicious activity reports, draft STR, STR narrative, file suspicious activity, AML STR, goAML, FinCEN SAR, suspicion narrative, or MLRO report. Guides jurisdiction-agnostic STR/SAR drafting—narrative structure (who, what, when, where, why suspicious), red flags and typologies, transaction aggregation and chronology, subject identification fields, supporting documentation checklists, quality review before filing, and escalation to MLRO/compliance—not TM rule building (aml-compliance), full LE case management, legal filing duty determination (commercial-counsel), or deep blockchain tracing (blockint skills). Complements aml-compliance, aml-cft, auditor, compliance-engineer, and commercial-counsel.
Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
Always-on ambient signal capture. Fires on every inbound message to detect original thinking and entity mentions. Spawn as a cheap sub-agent in parallel, never block the main response.
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
Design end-of-article CTAs (calls-to-action placed at the bottom of blog posts, newsletters, essays, articles, or any long-form content). Use this skill whenever the user asks to write, design, review, or improve a CTA at the bottom of an article, blog post, or essay; mentions "end-of-post CTA", "bottom of the article", "call-to-action", "signup box", "newsletter CTA", "subscribe block", "what should I put at the bottom", "how do I get readers to subscribe / share / book a call / buy / follow / join / download"; or asks how to convert article readers into subscribers, leads, customers, community members, or supporters. Also trigger when the user wants A/B testing guidance or accessibility review for a CTA block. Covers independent / personal writing, newsletter publications, and brand / content-marketing blogs across any topic — tech, finance, food, climate, design, lifestyle, B2B, B2C. Produces both the copy (content) and the structural / visual design (form), matched to the user's objective and audience.
One book → a clear "Viewfinder" → a 2050 Library Borrow Card (PNG). The card includes the real book cover, author's avatar, and book information; the Viewfinder block fully, fluently, and clearly expresses the book's unique "way of seeing the world". The illustration block uses a hand-drawn explanatory style with white background and black ink, featuring the ink portrait of Ji Gang himself (created by cutting out his avatar), turning this set of ideas into a vivid, easily understandable scene. Light optical glass style, the card's accent color is dynamically extracted from the book cover, with adaptive width and height. Remember this "pair of eyes" after closing the book, and your reading won't be in vain. Use when user says '取景框卡', '图书馆卡', 'library card', '书卡', '铸书卡', '一本书一句话一张卡', '/ljg-library', or provides a book name and wants it distilled into one collectible card. NOT FOR book structure analysis (use ljg-book), pure text golden quotes (use ljg-card -b), infographics (use ljg-card -i), visual notes (use ljg-card -v).
Use whenever you need an email address to receive something and then read or wait for it, especially during a signup or login flow. PROACTIVELY, and you can usually do this without asking the user first: a service is about to send a verification code, OTP, one-time code, 2FA or two-factor code, confirmation link, magic link, or password reset and you need to wait for it and read the value out; you are signing up for or registering with a service and must confirm an email address to continue; you need a fresh, managed, throwaway, or burner address instead of using a real one; you sent something and need to watch for what lands. REACTIVELY: the user asks "did it arrive?", "check the inbox", "what came in?", "wait for the email", or wants an address to catch replies, codes, receipts, or alerts. Provides a managed `*.primitive.email` address plus `primitive emails latest` and `primitive emails wait` to read and block for mail, and hosted Functions to run JavaScript on every inbound message. No SMTP, no DNS, no mail server. Use this when a third party sends mail TO you; to send your own message and wait for its reply, use the primitive-chat skill. Gets a free `*.primitive.email` address via `primitive agent start-agent-signup` if you do not already have one. Part of the Primitive CLI (Primitive, primitivedotdev, primitive.dev; the `primitive` or `prim` command).
Split plans, specs, or current conversations into a set of tracer-bullet tickets, each declaring blocking edges, and publish them to the configured tracker; use text edges in per-ticket files locally, and native blocking links in real trackers.
Answers questions about Amazon Application Recovery Controller (ARC) Region switch including architecture, plans, execution blocks, workflows, triggers, active/active vs active/passive, cross-account support, recovery time, dashboards, and customer positioning. Applicable when users ask about ARC Region switch adoption, design, or troubleshooting.