원클릭으로 Manus에서 모든 스킬 실행

시작하기

team-coordination

스타0

포크0

업데이트2026년 7월 1일 15:15

Team workflow rules. Use at conversation start to check TEAM_STATUS.md, ask user role, and prevent duplicate work.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Bobr2610

Bobr2610/materials-kg

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Team Coordination

At Conversation Start

Read TEAM_STATUS.md
Show current team status to user
Ask: "What is your role in the team?"
Ask: "What task would you like to work on?"
Check: does this overlap with other team members?

Team Roles

Role	Focus
ML / NLP / Knowledge Graphs	Embeddings, graph algorithms, entity extraction
Data Scientist	Metrics, benchmarks, experiments
Архитектор	Architecture, API contracts, system design
Материаловед	Domain knowledge, scientific accuracy
Product	Requirements, user stories, prioritization

When Starting Work

Update TEAM_STATUS.md:

| ML / NLP | YourName | Task description | в работе | feat/your-branch | 2026-07-01 |

When Finishing Work

Move your row to "История выполненных задач", set status to готово.

Rules

NEVER duplicate work from other team members
ALWAYS read TEAM_STATUS.md before starting
ALWAYS update TEAM_STATUS.md when starting/finishing
NEVER delete other participants' entries
Statuses: открыта | в работе | ожидает проверки | готово | заблокировано

이 저장소의 다른 Skills

같은 저장소

code-style

Bobr2610/materials-kg

Python code style and knowledge graph conventions for materials-kg. Use when writing or reviewing Python code.

2026-07-010

mimo-subagent

Bobr2610/materials-kg

Reusable MiMo CLI orchestration skill for delegating work to MiMo across any project. Use this skill whenever the user asks to use mimo, MiMo CLI, mimo run, mimo-auto, MiMo as a subagent, an external autonomous agent, or wants a task delegated to MiMo for research, coding, or summarization. Prefer this skill even when the user does not explicitly mention a skill but clearly wants work routed through MiMo.

2026-07-010

critical-thinking

Bobr2610/materials-kg

Anti-yes-man rules. Use before writing code, reviewing proposals, or responding to user suggestions.

2026-07-010

docker-workflow

Bobr2610/materials-kg

Docker commands and rules for materials-kg. Use when running the app, testing in containers, or rebuilding after code changes.

2026-07-010

materials-knowledge-graph

Bobr2610/materials-kg

Use for materials science knowledge graph tasks — extracting entities, building graph, querying by material/mode/property, finding data gaps, or any task involving the kg_engine/ module. Triggers on materials science queries, alloy/property extraction, graph construction, gap analysis, or hybrid search.

2026-07-010

name	team-coordination
description	Team workflow rules. Use at conversation start to check TEAM_STATUS.md, ask user role, and prevent duplicate work.

Team Coordination

At Conversation Start

Read TEAM_STATUS.md
Show current team status to user
Ask: "What is your role in the team?"
Ask: "What task would you like to work on?"
Check: does this overlap with other team members?

Team Roles

Role	Focus
ML / NLP / Knowledge Graphs	Embeddings, graph algorithms, entity extraction
Data Scientist	Metrics, benchmarks, experiments
Архитектор	Architecture, API contracts, system design
Материаловед	Domain knowledge, scientific accuracy
Product	Requirements, user stories, prioritization

When Starting Work

Update TEAM_STATUS.md:

| ML / NLP | YourName | Task description | в работе | feat/your-branch | 2026-07-01 |

When Finishing Work

Move your row to "История выполненных задач", set status to готово.

Rules

NEVER duplicate work from other team members
ALWAYS read TEAM_STATUS.md before starting
ALWAYS update TEAM_STATUS.md when starting/finishing
NEVER delete other participants' entries
Statuses: открыта | в работе | ожидает проверки | готово | заблокировано