Skills.
Give your AI a better way to work.
A skill is a set of written instructions that teaches an AI how to do one job the way it should be done: review a pull request, plan a migration, write the release notes.
Install one here and it travels with your account into Claude, Claude Code, Cursor and every other client you sign in with.
Category: Dev tools
16,902 results · page 391 of 564
- View details
index-description-allSkillDev tools
Query basic information for all indices (market.ft.tech). Use when the user asks for the full list of indices, index abbreviations and full names, index PB/PE TTM, the list of supported indices, or which indices are available.
Ready to connect★ 64
- View details
index-description-paginatedSkillDev tools
Contains index code (pure 6-digit `index_code`), name, summary, and other description fields. Use when the user asks for paginated index descriptions, a list of index summaries, the summary of a specific index, or what index descriptions exist. Also serves as a name-to-code mapping source: when the
Ready to connect★ 64
- View details
index-minutesSkillDev tools
Historical minute-level index quotes. Requires --symbol; optional date and pagination parameters. Use when the user asks about historical minute-level index quotes.
Ready to connect★ 64
- View details
index-minutes-batchSkillDev tools
Batch query historical minute-level K-lines for indices. Use when the user asks for minute-level quotes of multiple indices.
Ready to connect★ 64
- View details
index-weight-listSkillDev tools
Paginated query for index constituent weight details (market.ft.tech). Required: index_code; optional: date, pagination. Each entry includes constituent code, name, weight, and the url_hash for that period. Use when the user asks about index constituent weights, CSI 300 weight list, weights for a sp
Ready to connect★ 64
- View details
init-deps-installSkillDev tools
Automatically triggered when Tapestry is first launched on a new environment or lacks dependencies. Intelligently detects environment and installs Tapestry dependencies with user confirmation.
Ready to connect★ 64
- View details
institution-share-holdingsSkillDev tools
Query institutional share holdings. Endpoint: GET /api/v2/market/data/institution/institution-share-holdings. All requests must set FTSHARE_API_KEY.
Ready to connect★ 64
- View details
kata-complete-milestoneSkillDev tools
Use when the user wants to finish, close, ship, archive, or mark the active Kata milestone complete.
Ready to connect★ 64
- View details
kata-execute-issueSkillDev tools
Use when the user wants to execute a standalone Kata issue, one-off issue plan, backlog issue, or isolated implementation plan created by kata-plan-issue. This skill selects or retrieves an open issue from the backend, confirms the issue with the user, then executes its approved plan with fresh suba
Ready to connect★ 64
- View details
kata-healthSkillDev tools
Use when the user asks whether Kata is configured correctly, healthy, connected, or ready to run.
Ready to connect★ 64
- View details
kata-new-milestoneSkillDev tools
Use when the user wants to create the next milestone, release goal, or scoped delivery target for an existing Kata project.
Ready to connect★ 64
- View details
kata-new-projectSkillDev tools
Use when the user wants to start, define, import, or initialize a Kata project.
Ready to connect★ 64
- View details
kata-update-projectSkillDev tools
Use when the user wants to update an in-flight Kata project, refresh project artifacts, revise the current milestone, adjust requirements or roadmap context, or pause work to record ad hoc project direction changes. This skill interactively updates durable project and active milestone artifacts with
Ready to connect★ 64
- View details
kata-verify-workSkillDev tools
Use when the user asks to verify, validate, review, or sign off on Kata work.
Ready to connect★ 64
- View details
kline-pattern-annotationsSkillDev tools
Query K-line pattern annotations. Endpoint: GET /api/v3/market/data/kline-pattern-annotations. All requests must set FTSHARE_API_KEY.
Ready to connect★ 64
- View details
lamprey-change-controlSkillDev tools
How changes are classified, gated, approved, committed, and shipped in the Lamprey Harness repo. Load this BEFORE making any change — code, docs, config, or release — or when you see terms like P-SPR, STS, verify gate, era-lock, commit trailer, push policy, or when a commit/push is rejected by a hoo
Ready to connect★ 64
- View details
lamprey-loop-reliability-campaignSkillDev tools
The executable, decision-gated campaign for Lamprey's hardest live problem — proving loop autonomy (interval / self-paced / autonomous backlog) reliable in real use. Numbered phases with exact commands, expected observations at every gate, a ranked solution menu for failures, fenced-off wrong paths,
Ready to connect★ 64
- View details
lamprey-research-methodologySkillDev tools
The discipline that turns a hunch into an accepted result in Lamprey — the evidence bar (one mechanism explains all observations including negatives, and survives refutation), numbers predicted before running, the full idea lifecycle from hunch to adopted change or documented retirement, and where g
Ready to connect★ 64
- View details
lamprey-ship-and-releaseSkillDev tools
How Lamprey runs and ships — run modes, userData layout, Windows release artifacts, the one-command "Bucket" pipeline, macOS/Linux CI mirroring, GitHub publication, CDN purge, and failure recovery. Load when the user says "ship", "release", "tag it", "Bucket", or when a release step fails partway.
Ready to connect★ 64
- View details
libor-dailySkillDev tools
Query daily international benchmark rates. Endpoint: GET /api/v1/market/data/libor-daily. All requests must set FTSHARE_API_KEY.
Ready to connect★ 64
- View details
limit-event-timelineSkillDev tools
Query the limit-up/limit-down event timeline. API: GET /api/v2/market/data/limit-event-timeline-3s. All requests must set FTSHARE_API_KEY.
Ready to connect★ 64
- View details
limit-listSkillDev tools
Query the limit-up/limit-down pool. API: GET /api/v1/market/data/limit-list. All requests must set FTSHARE_API_KEY.
Ready to connect★ 64
- View details
limit-up-briefsSkillDev tools
Query limit-up briefs. Endpoint: GET /api/v3/market/data/limit-up-reports/briefs. All requests must set FTSHARE_API_KEY.
Ready to connect★ 64
- View details
limit-up-public-reportSkillDev tools
Query the public limit-up attribution report. API: GET /api/v3/market/data/limit-up-reports/public-report. All requests must set FTSHARE_API_KEY.
Ready to connect★ 64
- View details
major-contract-by-dateSkillDev tools
Query A-share major contract information by announcement date range (market.ft.tech). Use when the user asks about major contracts, major contracts on a specific day or month, contract amounts, or signing parties.
Ready to connect★ 64
- View details
major-contract-by-symbolSkillDev tools
Query major contract history by stock symbol (market.ft.tech). Use when a user asks about a stock's major contracts, what big deals a company has signed, or contract amounts.
Ready to connect★ 64
- View details
major-contract-summarySkillDev tools
Ranked summary of major contracts for A-share stocks over the past year (market.ft.tech). Use when the user asks about major contract rankings, which companies signed the most/largest contracts, or total contract value rankings.
Ready to connect★ 64
- View details
market-distribution-intradaySkillDev tools
Query intraday market rise/fall distribution. Endpoint: GET /api/v2/market/data/market-distribution-intraday. All requests must set FTSHARE_API_KEY.
Ready to connect★ 64
- View details
member-build-processSkillDev tools
Queries a single futures member's position changes for a specified contract/date range, and estimates daily and cumulative profit/loss combined with contract quotes. Use when the user mentions "会员建仓过程", "期货会员持仓盈亏", "会员净持仓变化", or "member build process". Supports filtering by exchange/member/contract,
Ready to connect★ 64
- View details
namechangeSkillDev tools
Queries former names of A-share stocks. Use when the user asks about a stock's former names, historical names, name change records, what it was previously called, original name, stock name changes, e.g. '600848 曾用名' or '自仪股份改名'. Parameter trade_code is required and must include a .SZ/.SH suffix; mul
Ready to connect★ 64
What is a skill?
A skill is plain text, usually a SKILL.md file and the scripts it refers to, written for an AI rather than for a person. It carries the steps, the house rules and the examples a good answer needs, so you stop pasting the same briefing into every new chat.
53,789 of the 54,221 skills listed here can be served through ahel today, and they come from public repositories. Each one has its own page with the instructions themselves on it, so you can read what a skill will tell your AI to do before you install it.
Install one and every AI you use gets it
Installing a skill adds it to your gateway and turns it on in the same step. Claude Code surfaces it as a slash command; any client can read the full instructions with the skill_read tool.
Nothing is copied into a project folder. The instructions are served from your account, so the same skill is there in every AI you connect, and turning it off removes it from all of them at once.