## 1. Define a small shared job and source list

Inventory the two definitions, snapshot interval and four questions. List authorized sources, excluding private conversations and client lists. Draft a Team Bot job description; do not create or publish a Bot.

Expected: A job focused on two metrics.
Check: No private chats or unauthorized customer data become reference material.

## 2. Bind every metric to a period and denominator

Create a D01/D02 dictionary with event, unique entity, time field, Asia/Shanghai and half-open snapshot interval. Ask for Q03’s conversion action and denominator before ranking.

Expected: Two definitions and a Q03 clarification list.
Check: Counts differ and the exclusive end date is explicit.

## 3. Answer supported questions and expose gaps

Answer Q01–Q04 with D ids and the snapshot interval. Do not invent Q03 data or provide Q04 private information. Save answers.md only; do not connect a warehouse or post to Slack.

Expected: Four cited answers.
Check: Q01 is 42; Q02 is 105; Q03 has no invented ranking.

## 4. Review shared settings and memory candidates

Draft a checklist of shared files/Skills, connector login mode, credential scope, memory candidates and owner. Recommend only general D01/D02 definitions, not client details or personal chat. Include no secrets and publish nothing.

Expected: A configuration and memory review list.
Check: General definitions and private data stay separate; shared credentials are not described as isolated.

## 5. Test read-only answers with different members

After owner setup on desktop, have two test members ask the same read-only question. Record accounts, visible sources, results and missing-permission messages. Use small aggregate data only. Review before publishing; users complete login and consent.

Expected: A member-by-member access comparison.
Check: A member lacking permission does not receive data through someone else’s account.

## 6. Version definitions with an owner

Draft a metric-answer Skill with source version, period, definition, citations, clarification and permission handling. Submit memory updates for owner review with effective time and reason. Do not silently overwrite definitions or notify all members.

Expected: A maintainable answering standard.
Check: Old/new definitions are traceable; no unreviewed team-memory write occurs.