Loading...
Loading...
Found 753 Skills
Benchmark any agent skill to measure whether it actually improves performance. Use when the user wants to evaluate, test, or compare a skill against baseline, or when they mention "benchmark", "eval", "skill performance", or "does this skill help". Runs isolated eval sessions with and without the skill, grades outputs via layered grading (deterministic checks + LLM-as-judge), analyzes behavioral signals, and generates a comparison report with a USE / DON'T USE verdict.
Search and analyze research papers, find related work, summarize key ideas. Use when user says "find papers", "related work", "literature review", "what does this paper say", or needs to understand academic papers.
Systematic 4-phase codebase exploration: Detect, Explore, Map, Summarize. Use when starting work on an unfamiliar codebase, onboarding to a new project, reviewing a repository for the first time, or building context before debugging or code review. Use for "explore codebase", "what does this project do", "understand architecture", or "onboard me". Do NOT use for modifying files, running applications, performance optimization, or deep domain analysis.
Transform dense technical communication into clear, structured business formats using proposition extraction and deterministic templates. Use when user needs to convert technical updates, debugging narratives, status reports, or dependency discussions into executive-ready summaries. Use for "transform this update", "make this executive-ready", "summarize for my manager", "professional format", or "status report". Do NOT use for writing new content from scratch, creative writing, or generating documentation that doesn't transform an existing input.
Read Discord for financial research using the discord-cli tool (read-only). Use this skill whenever the user wants to read Discord channels, search for messages in trading servers, view guild/channel info, monitor crypto or market discussion groups, or gather financial sentiment from Discord. Triggers include: "check my Discord", "search Discord for", "read Discord messages", "what's happening in the trading Discord", "show Discord channels", "list my servers", "Discord sentiment on BTC", "what are people saying in Discord about AAPL", "monitor crypto Discord", "export Discord messages", any mention of Discord in context of reading financial news, market research, or trading community discussions. This skill is READ-ONLY — it does NOT support sending messages, reacting, or any write operations.
Push the current branch to origin safely (lint, test, resolve non-fast-forward via pull skill, then push). Use when the user asks to push or publish commits to the remote. Does not create or edit PRs—use the create-pr-jp skill for that.
Merge the latest default branch (e.g. origin/main) into the current branch, resolve merge conflicts, and verify with pnpm lint && pnpm test. Merge-based sync (not rebase) unless the repo specifies otherwise. Use when syncing a feature branch with origin, after a non-fast-forward push, or when the branch is behind. Does not push or manage PRs—use push and create-pr-jp for those.
Systematic retrieval expert covering all areas of Chinese law. ## Core Features - Supports user identity recognition (ordinary person/law student/lawyer/judge/prosecutor) - Provides differentiated services based on different identities - Complete legal source retrieval (laws/administrative regulations/judicial interpretations/guiding cases/typical cases) - Original legal article citation and cross-reference sorting ## Core Trigger Conditions (Trigger if any is met) **High Priority (Must Trigger)**: - Explicit request to find legal articles/regulations/judicial interpretations/regulatory documents - Request to determine legality/illegality ("Is it illegal?""Is it legal?""Am I liable?") - Request to find compensation standards/compensation amounts/liability determination/procedural requirements - Asking "Based on which law?""What does the law stipulate?""What is the legal basis?" **Medium Priority (Trigger based on context)**: - "What to do?""How to defend rights?""Can I sue?" - "What procedures are needed?""What conditions are required?" - "What else can I claim?""Where can I file a complaint?" ## Application Scenarios - Labor disputes: illegal termination, economic compensation, work-related injuries, social security, job transfer, etc. - Contract disputes: deposit, liquidated damages, breach of contract liability, sales contracts, etc. - Tort liability: traffic accidents, personal injury, medical accidents, environmental pollution, etc. - Marriage and family: divorce property, child custody, estate inheritance, etc. - Administrative/criminal/corporate finance, etc. ## Non-Triggering Scenarios - Only asking about legal concepts/terminology explanations (not retrieval-related) - Only requesting lawyer/legal service recommendations - Only discussing legal news/case stories (not involving specific regulations) - Only asking about legal examination/study questions **Note**: Even if the user does not explicitly request a "retrieval report", this skill will be triggered as long as the issue involves searching, organizing, interpreting, or applying legal norms.
Must be followed when writing error handling code that includes try-catch. Ensure that the catch block has substantial processing logic, is not empty, does not only log information, and must handle or re-throw exceptions. Trigger keywords: try-catch specification, error handling best practices, exception handling review.
Evaluate the output of a journey-builder run, identify instruction gaps, and edit the project root AGENTS.md (or add pitfalls to the gist) to fix those gaps. Does NOT modify the journey-builder skill itself.
Create subtasks in Jira from a previously generated task plan. Reads the plan from docs/<TICKET_KEY>-tasks.md and creates one Jira subtask per task under the parent ticket. Use when the user says "create subtasks", "push tasks to Jira", "sync plan to Jira", "create Jira tickets", "make subtasks for PROJECT-1234", or anything about turning a plan into Jira issues. Also triggered by the orchestrating-jira-workflow skill as Phase 4. Requires the task plan to already exist (run planning-jira-tasks first if it does not). Use this skill even if the user just says "push to Jira" or "create the tickets" after a planning phase — those are subtask creation requests.
Retrieve ALL information from a Jira ticket (description, comments, subtasks, attachments metadata, labels, sprint, status, assignee, reporter, linked issues, custom fields, acceptance criteria) and persist it as a single Markdown file. Use whenever the user says "fetch ticket", "retrieve Jira", "pull ticket info", "get ticket details", "look up ticket", "grab the Jira", "what does ticket X say", "check the ticket", "read the ticket", "show me the ticket", or provides a Jira ticket URL or key like PROJECT-1234. Also triggered by the orchestrating-jira-workflow skill as Phase 1 of the end-to-end pipeline. Trigger even if the user only pastes a ticket key with no other context — that alone means "fetch this ticket." This skill ONLY retrieves — it never modifies the ticket or starts implementation.