Verify code changes by running the project's typecheck, build, lint, and targeted tests, then fix and re-run until clean. Use after editing any source file.
日本語の概要は準備中です。原文の説明を表示しています。
236 件(agentscope-ai のリポジトリ) ・ 人気順
概要と使いどころ
Verify code changes by running the project's typecheck, build, lint, and targeted tests, then fix and re-run until clean. Use after editing any source file.
日本語の概要は準備中です。原文の説明を表示しています。
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for a summary, TL;DR, or condensed version of any content.
日本語の概要は準備中です。原文の説明を表示しています。
First-response playbook for an inbound customer message — classifies the ticket, restates the issue, gathers missing context, and routes the reply.
日本語の概要は準備中です。原文の説明を表示しています。
Answer a quantitative business question by writing a SQL query against the data warehouse, validating it, and presenting the result. Use when the user asks "how many...", "what's the trend of...", "compare X vs Y over...", "what's our top N...", or anything that resolves to a query against tabular data. Produces a small result table plus the underlying query.
日本語の概要は準備中です。原文の説明を表示しています。
Statistical data analysis skill — use when the user asks to analyze numbers, compute statistics, or summarize datasets.
日本語の概要は準備中です。原文の説明を表示しています。
Search a codebase efficiently with ripgrep regular expressions, file globs, and git history search. Use to locate symbols, usages, and definitions instead of reading whole files.
日本語の概要は準備中です。原文の説明を表示しています。
Expert Java developer skill for AgentScope Java framework - a reactive, message-driven multi-agent system built on Project Reactor. Use when working with reactive programming, LLM integration, agent orchestration, multi-agent systems, or when the user mentions AgentScope, ReActAgent, Mono/Flux, Project Reactor, or Java agent development. Specializes in non-blocking code, tool integration, hooks, pipelines, and production-ready agent applications.
日本語の概要は準備中です。原文の説明を表示しています。
Apply multi-file or tricky edits atomically with git apply instead of many fragile edit_file calls. Use when changing several files at once or when edit_file fails to match.
日本語の概要は準備中です。原文の説明を表示しています。
Use when admin gives a task to delegate to a Worker, when a Worker reports task completion, when managing recurring scheduled tasks, or when you need to check worker availability.
日本語の概要は準備中です。原文の説明を表示しています。
Use for standalone Matrix admin requests (register users, create rooms, manage membership, upload files). Also use when you need to send a file to the admin via Matrix media upload. Do NOT use for Worker/project creation — those handle Matrix operations internally.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a QwenPaw-backed Worker needs to decide whether to do work directly, use native subagents for internal parallelism, or create a temporary QwenPaw agent with a custom AGENTS.md and skills.
日本語の概要は準備中です。原文の説明を表示しています。
Use before sending or suppressing any Leader message to Workers, Manager, or Team Admin. Always use this skill for cross-room Matrix messages, @mention decisions, task assignment notifications, structured status reports, completion reports, blocker/revision messages, questions, requester updates, or when deciding whether a same-room reply is enough.
日本語の概要は準備中です。原文の説明を表示しています。
Use before direct filesync calls, reading non-task shared files, pushing mid-task progress, or troubleshooting missing shared files. Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you are invited to a Project Room or assigned a task within a multi-worker project. Covers project plan reading, task coordination with other Workers, and git author config.
日本語の概要は準備中です。原文の説明を表示しています。
Switch a Worker Agent's LLM model via agt CLI. Use when the human admin requests changing a Worker's model.
日本語の概要は準備中です。原文の説明を表示しています。
Use only when you need to look up team topology, worker phase, runtime state, or identity that is NOT available from the current message context. Do not use for standard task flows — the coordinator is the message sender, and the task room is in meta.json.room_id.
日本語の概要は準備中です。原文の説明を表示しています。
Use when admin requests adding a human user to the system, changing human permissions, removing human access, or managing human accounts.
日本語の概要は準備中です。原文の説明を表示しています。
Use when determining sender identity in any room, managing trusted contacts, configuring the admin's primary notification channel, handling first-contact from a new channel, or escalating to admin across channels.
日本語の概要は準備中です。原文の説明を表示しています。
Use as a helper when the admin is assigning work but has not specified an existing Worker, so you need to search Nacos for a suitable Worker and ask whether to import it; also use when the admin explicitly says to import a Worker from the market or gives a direct nacos package URI.
日本語の概要は準備中です。原文の説明を表示しています。
Execute AI coding CLI tools (Claude Code / Gemini CLI / qodercli) on behalf of Workers. Use when a Worker sends a coding-request: message, asking Manager to run coding operations in their workspace.
日本語の概要は準備中です。原文の説明を表示しています。
Use for TeamHarness shared workspace paths, filesync, artifact publication, and Matrix room file boundaries, including artifact publish_file and task/project deliverables. Do not use for message routing or project state changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use before deciding how you should organize team work: DAG vs Loop, dependency shape, task waves, quality gates, acceptance criteria, interruption, replanning, or what to do after Worker results arrive. Always use this skill for team organization strategy before you call project-management or task-management.
日本語の概要は準備中です。原文の説明を表示しています。
Use before sending @mentions, deciding whether to reply, TASK_COMPLETED, BLOCKED, QUESTION, direct answers, loop prevention, or suppressing low-information acknowledgements.
日本語の概要は準備中です。原文の説明を表示しています。