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

team-intro

스타32

포크9

업데이트2026년 4월 29일 07:17

Use this skill when the user asks what you know about them, the team, their projects, or their systems - especially in an onboarding framing like "tell me about the team", "onboard me", "what do you know about us", "who's on the team", "what systems do we own", "what can you do for me", or any variant of "what do you know about me and the team". Also trigger when a new person is being onboarded or when the user asks for a team/project overview.

설치

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

Manus에서 실행

출처

michaelimas1

michaelimas1/team-context-template

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

다운로드

Manus에서 실행

Team Intro

Build a comprehensive team overview from these sources:

Read CLAUDE.md — team identity, systems table, task routing, workflow conventions
Read references/team.md — full roster with Slack IDs, GitHub logins, emails
Read references/slack.md — channel directory
Read PHILOSOPHY.md — how the team context works and why

Present the information in a clear, structured format. Cover:

Who the team is and what they own
The systems landscape (owned vs reference)
Key workflow conventions
What Claude can do for them (skill categories)
How to get started (recommended reading: PHILOSOPHY.md, then system docs as needed)

Do not recall memories. Build the overview entirely from the repo files above.

이 저장소의 다른 Skills

같은 저장소

curious-intern

michaelimas1/team-context-template

Use this skill when the user has spare time and wants to improve the knowledge base by being interviewed about gaps. Triggered by "curious intern", "interview me", "extract knowledge", "fill gaps", "what's missing in the docs", "brain dump", "ask me questions about our systems", "I have spare time", "teach you something". This is the "Let the AI Interview You" philosophy principle as a repeatable workflow.

2026-04-2932

good-morning

michaelimas1/team-context-template

Use this skill when the user says "good morning", "morning brief", "daily brief", "daily standup", "catch me up", "what happened overnight", "what's going on today", "start of day", or wants a daily summary of their tasks, team PRs, and Slack activity. Generates a structured morning brief covering active sprint tasks with burndown, unowned bugs, key Slack highlights, PRs open for review, and PRs merged in the last 24 hours.

2026-04-2932

health-check

michaelimas1/team-context-template

Use this skill when the user wants to check the health of the team context, find stale docs, missing fields, or template compliance issues. Triggered by "health check", "check repo health", "stale docs", "team context health", "are our docs up to date", "what needs updating", "doc hygiene", "review system docs". Good to run during sprint retros or after major infrastructure changes.

2026-04-2932

list-skills

michaelimas1/team-context-template

Use this skill when the user asks to "list skills", "show skills", "what skills are available", "available skills", "skills list", "skill shortcuts", "show shortcuts", "what can you do", "what skills do we have", "show me the skills", or wants to see an overview of all team skills and how to trigger them. Always use this skill instead of summarizing from memory - the list is read live from the skills directory.

2026-04-2932

pm-story

michaelimas1/team-context-template

ALWAYS use this skill - do not call Monday MCP tools directly - when the user wants to write, document, update, or create a product story or task. Triggered by ANY of these: "pm-story", "write a story", "document this task", "update this task", "fill in this task", "write up this task", "log this idea", "track this", "add this to the board", "open a task for X", "create a task", "add a task", "log an issue", "I found a bug", "track this issue", "add this to the sprint", or any message that includes a Monday task URL with intent to document or fill in product context.

2026-04-2932

retro

michaelimas1/team-context-template

Use this skill when the user wants to capture learnings from a completed workflow, save knowledge for next time, update a skill or system doc based on what was discovered, or reflect on what went well/poorly. Triggered by "let's retro", "capture what we learned", "save this for next time", "update the skill", "what did we learn", "document this for next time", "don't forget this", "we should remember this". Also suggest this skill proactively after completing a novel or complex workflow.

2026-04-2932

name

team-intro

description

Team Intro

Build a comprehensive team overview from these sources:

Read CLAUDE.md — team identity, systems table, task routing, workflow conventions
Read references/team.md — full roster with Slack IDs, GitHub logins, emails
Read references/slack.md — channel directory
Read PHILOSOPHY.md — how the team context works and why

Present the information in a clear, structured format. Cover:

Who the team is and what they own
The systems landscape (owned vs reference)
Key workflow conventions
What Claude can do for them (skill categories)
How to get started (recommended reading: PHILOSOPHY.md, then system docs as needed)

Do not recall memories. Build the overview entirely from the repo files above.