Total 59,120 skills
Showing 12 of 59120 skills
Lewis's backtest workflow. Drop a strategy idea in, get a structured backtest plan and results template back.
Pre-trade risk check. Position sizing, stop placement, R-multiple math — before you click the button, not after.
Synthetic terminal-style screen recording guidance for Remotion `TerminalScene`.
Japanese-language skill that supports discovery, comparison, installation, and add-mcp connection of public MCP (Model Context Protocol) servers. Actively use this skill when receiving requests such as 'Is there an MCP server for XX?', 'Find MCP tools', or 'I want to install via add-mcp' for tasks like DB integration, external API access, file operations, GitHub collaboration, etc., and handle everything from candidate discovery to operation testing. If the 'find-mcp-server' skill exists separately, only load 'find-mcp-server-ja' and never load both 'find-mcp-server' and 'find-mcp-server-ja'.
Check whether an SDK version supports a RevenueCat feature, whether an SDK upgrade is required, why an SDK-gated feature is not working, or how much of a project's recent subscriber base is on incompatible SDK versions. Use for questions about RevenueCat SDK compatibility, feature gates, minimum SDK versions, SDK adoption, upgrade impact, and rollout risk.
Reference for the uploads CLI and its stdio/hosted MCP tools — exact flags, keys, and contracts for put and attach, screenshot capture, stable PR/issue keys, the managed attachments comment, metadata and search, galleries, config defaults, login/doctor, and output formats. Use when driving the `uploads` CLI or its MCP tools (including the hosted MCP at agents.uploads.sh for agents without local filesystem/git access), when you need a public URL for a local file ("upload this", "host this image", "give me a public URL for this file"), when the CLI itself prints a hint or nudge you need to act on (a `hint` field in `--format json`, or the stderr note suggesting `--pr`/`attach --branch`), or when you need exact flags, key layouts, or setup and auth details. For the when-and-how of getting a screenshot or recording into a GitHub PR or issue, start with the github-screenshots skill — it defers here for CLI detail.
Agent Session Visualization / Session Timeline: Execution maps for Cursor, Codex, Claude Code, Workbuddy, kimi-code threads (by ID or name); includes skills/tools/sub-agents, retries/forks/waits, layered internationalization + session health. Triggers (English): agent thread visualizer, agent-thread-visualizer, agent session timeline, session report, session log analyzer, agent flow visualization, execution map, conversation visualizer, subagent timeline, debug agent session, visualize the run, Cursor session, Claude Code session, Workbuddy session, kimi-code session. (Chinese): agent session visualization, session visualization, agent timeline, sub-agent visualization, session report, session analysis, execution map, agent execution flow, debug agent session, Cursor session, Claude Code session, Workbuddy session, kimi-code session. (Japanese): agent session visualization, session visualization, agent timeline, sub-agent visualization, session report, execution map, agent execution flow, Cursor session, Claude Code session, Workbuddy session, kimi-code session.
By identifying and leveraging potential differences (efficiency/scale/cognition/gravitation), choose to stand in a high-potential position to amplify the competitiveness of individuals or organizations. Applicable to scenarios such as career choice, entrepreneurial direction judgment, and industry trend analysis. Use this skill when you face decisions like "which platform/company/industry to choose" or want to understand why there is a huge gap in results despite similar efforts. Not applicable to the execution stage where you have locked onto a track and can only work hard (you should return to improving specific abilities at this time), nor to pure internal management optimization (potential is an external lever). Key trigger signals: "Why am I not succeeding despite working so hard?", "Choose industry A or B?", "Does this industry have a future?", "How to leverage momentum?"
A framework for analyzing and solving problems using the NLP Logical Levels model. Use it when you're stuck in a dilemma without a way out, keep going in circles at the same level, or need to make major life decisions. The six levels from lowest to highest are: Environment → Behavior → Capability → BVR (Beliefs/Values/Rules) → Identity → Spirit. Core method: Design your life from the top down, solve problems that can't be resolved at lower dimensions by elevating your perspective. Not applicable to daily operational issues (e.g., how to write an email). Key trigger signals: "What should I do?", "Why do I always encounter the same problem?", "I don't know how to choose.", "I'm confused about my life direction."
Revealing AI capability gradually to match user mental models.
Correct, create, or remove written material so a later reader can rely on it: documentation that no longer matches the system, a fact about to be written down a second time, prose restating what a config file or command already prints, a records folder that has drifted, or a decision worth recording so it stops being re-argued. Prose no human has read counts as a hypothesis, not a source. Use when the user says "the docs are out of date", "readme still says the old flow", "where does this go", "write this down", or "should this be an ADR". Not for judging docs inside a change under review, explaining an existing document, or looking up a third party documentation.
Scan dependencies for known vulnerabilities using OSV. Use when checking for CVEs, reviewing security posture, or investigating who introduced a vulnerable dependency.