{ "schemaVersion": "1.0", "item": { "slug": "team-status-tracker", "name": "Team Status Tracker", "source": "tencent", "type": "skill", "category": "通讯协作", "sourceUrl": "https://clawhub.ai/parthpandya1729/team-status-tracker", "canonicalUrl": "https://clawhub.ai/parthpandya1729/team-status-tracker", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/team-status-tracker", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=team-status-tracker", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md", "config.yaml", "templates/obsidian-tracking.md", "templates/status-request.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/team-status-tracker" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/team-status-tracker", "agentPageUrl": "https://openagent3.xyz/skills/team-status-tracker/agent", "manifestUrl": "https://openagent3.xyz/skills/team-status-tracker/agent.json", "briefUrl": "https://openagent3.xyz/skills/team-status-tracker/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Overview", "body": "Systematic approach to track team member status updates via Slack DMs with Obsidian-based internal tracking. Maintains confidentiality while gathering actionable project updates." }, { "title": "When to Use", "body": "Daily/weekly team status check-ins\nProject progress monitoring\nResource management and workload tracking\nIdentifying blockers and support needs\nBehavioral pattern analysis for team optimization" }, { "title": "Communication (Slack DMs)", "body": "✅ DO:\n\nSend personalized status requests (1-on-1 DMs)\nAsk specific questions about THEIR projects only\nRequest task IDs, timelines, specific blockers\nMaintain professional, supportive tone\nOffer help with blockers\nFollow up with non-responders (mid-day, EOD)\n\n❌ DON'T:\n\nShare financial information with resources (unless finance_transparency: 1 - see Configuration)\nShare billing amounts, revenue figures, client contracts (unless explicitly enabled)\nDiscuss other team members' performance publicly\nShare behavioral tracking notes with team (NEVER - always confidential)\nUse public channels for status requests (keep it private)" }, { "title": "Internal Tracking (Obsidian)", "body": "✅ Track (Confidential):\n\nResponse times (prompt, delayed, no response)\nResponse quality (detailed, vague, minimal)\nBehavioral patterns (proactive, reactive, non-responsive)\nCommunication effectiveness\nBlockers and support needs\n\n❌ Never Share with Team:\n\nThese tracking notes\nPerformance comparisons\nResponse time metrics\nNon-responder lists" }, { "title": "config.yaml", "body": "Create a configuration file at .openclaw/workspace/skills/team-status-tracker/config.yaml:\n\n# Team Status Tracker Configuration\n\n# Confidentiality Settings\nconfidentiality:\n # Financial information transparency\n # 0 = NEVER share financial info (billing, revenue, payments) with resources (DEFAULT)\n # 1 = Share financial context when needed (budget, project value, payment status)\n finance_transparency: 0\n \n # What to NEVER share regardless of transparency setting\n always_confidential:\n - Performance comparisons between team members\n - Behavioral tracking notes\n - Response time metrics\n - Non-responder lists\n - Internal strategy discussions\n\n# Slack Settings\nslack:\n check_interval_hours: 2 # How often to check for responses\n reminder_midday: true # Send mid-day reminder to non-responders\n reminder_eod: true # Send end-of-day reminder\n \n# Response Grading\nresponse_grading:\n excellent: \"<1h\"\n good: \"1-3h\"\n acceptable: \"3-6h\"\n delayed: \"6-12h\"\n poor: \">12h\"" }, { "title": "Using the Config", "body": "When finance_transparency: 0 (DEFAULT - Recommended):\n\n❌ DON'T share:\n\n\"This project is worth $50K\"\n\"Client is paying us $X/month\"\n\"You'll get paid when invoice clears\"\n\"Project budget is $XXX\"\n\"Client owes us money\"\n\n✅ DO share:\n\n\"This project is high priority\"\n\"Client needs this urgently\"\n\"This is a strategic client\"\nGeneral project scope and timeline\n\nWhen finance_transparency: 1 (Optional - Use with caution):\n\n✅ CAN share when contextually relevant:\n\n\"This project has a budget of $X - keep scope tight\"\n\"Client pays milestone-based, need to deliver by [date] for payment\"\n\"High-value client ($XX/month) - prioritize their requests\"\n\"We're waiting on client payment before next phase\"\n\n❌ STILL DON'T share:\n\nIndividual team member salaries or rates\nPerformance comparisons\nBehavioral tracking notes\nFull contract terms\nClient's internal budget/financials" }, { "title": "When to Enable Finance Transparency", "body": "Consider finance_transparency: 1 when:\n\n✅ Working with senior team members (leads, managers)\n✅ Team owns P&L responsibility\n✅ Budget constraints affect decisions\n✅ Payment delays impact work planning\n✅ Team needs context for scope/priority decisions\n\nKeep finance_transparency: 0 when:\n\n✅ Junior team members (default safe option)\n✅ Contractors/outsourced resources\n✅ Large team with varied seniority\n✅ Uncertain about team maturity\n✅ Company policy requires strict separation" }, { "title": "Message Examples by Config", "body": "Scenario: Team member asks about project priority/urgency\n\nWith finance_transparency: 0 (DEFAULT):\n\nThis is a strategic client for us - high priority.\nPlease prioritize their requests and maintain quality.\nLet me know if you need any support!\n\nWith finance_transparency: 1:\n\nThis is a high-value client ($X/month contract).\nProject budget is $Y - keep scope tight and deliver by [date].\nPayment is milestone-based, so meeting the deadline is critical.\nLet me know if scope creep becomes an issue!\n\nScenario: Team member asks why project is urgent\n\nWith finance_transparency: 0:\n\nClient needs this urgently for their Q1 launch.\nIt's a strategic partnership opportunity.\nCan you prioritize this over [other project]?\n\nWith finance_transparency: 1:\n\nClient needs this for Q1 launch - they've paid 50% upfront ($X).\nRemaining $Y comes on delivery by [date].\nCan you prioritize this? It's blocking our cash flow.\n\nScenario: Team member asks about changing scope\n\nWith finance_transparency: 0:\n\nLet's stick to the original scope for now.\nAny additions need client approval first.\nPlease document the request and I'll discuss with client.\n\nWith finance_transparency: 1:\n\nCurrent scope is fixed at $X - no room in budget.\nIf they want additions, we need to quote separately.\nPlease document the request with time estimate.\nI'll discuss pricing with client." }, { "title": "1. Morning: Send Status Requests", "body": "Send personalized Slack DMs asking ONLY about specific person's projects:\n\nHi [Name]! 👋\n\nQuick status check on *[Their Project]*:\n\n📊 Could you please share:\n• Current progress this week?\n• Any blockers or challenges?\n• Coordination with team smooth?\n• Support needed?\n\nThanks! 🚀\n\nKey Rules:\n\n✅ Personalize for each person's actual projects\n✅ Ask specific questions\n❌ NO commercial/payment info\n❌ Don't mention other projects they're not on" }, { "title": "2. Throughout Day: Monitor & Respond", "body": "Check Slack every 2-3 hours:\n\nWhen someone responds:\n\nRead their response in Slack\nAsk follow-up questions via Slack:\nThanks for the update! 👍\n\nCould you provide:\n📋 Specific task ID or ticket number?\n📊 Current progress % or milestone?\n⏰ Expected completion date?\n🚧 Any blockers preventing progress?\n\n\nUpdate internal Obsidian tracking\nNever share confidential info in responses\n\nWhen no response by mid-day:\n\nHi [Name]! 👋\n\nJust a friendly reminder - still waiting for your status update.\n\nWould appreciate a quick response when you get a chance. Thanks! 🙏" }, { "title": "3. End of Day: Final Nudge", "body": "For non-responders:\n\nHi [Name]! ⏰\n\nQuick reminder - please share your status update by end of day today.\n\nThis helps us track progress and provide support. Thanks! 🙏" }, { "title": "4. Track in Obsidian (Internal Only)", "body": "Create daily tracking files:\n\ndaily-status/\n├── YYYY-MM-DD/\n│ ├── TEAM STATUS - YYYY-MM-DD.md\n│ └── SUMMARY.md\n└── README.md (confidentiality rules)\n\nTrack for each person:\n\nResponse time\nResponse quality\nBehavioral pattern\nProject updates\nBlockers mentioned\nFollow-up needed" }, { "title": "Response Time Benchmarks", "body": "Excellent: < 1 hour\nGood: 1-3 hours\nAcceptable: 3-6 hours (same day)\nDelayed: 6-12 hours\nPoor: > 12 hours or no response" }, { "title": "🟢 Proactive", "body": "Responds quickly\nProvides detailed updates\nAnticipates questions\nAsks for clarification when needed" }, { "title": "🟡 Reactive", "body": "Responds when prompted\nBasic updates provided\nNeeds follow-up questions" }, { "title": "🔴 Non-Responsive", "body": "Delayed or no responses\nVague or incomplete updates\nRequires multiple nudges" }, { "title": "🚫 ALWAYS CONFIDENTIAL (Regardless of Config):", "body": "Performance comparisons between team members\nBehavioral tracking notes\nResponse time metrics\nNon-responder lists\nInternal strategy discussions" }, { "title": "💰 FINANCIAL INFO (Config-Dependent):", "body": "When finance_transparency: 0 (DEFAULT):\n❌ DON'T share: Payment amounts, billing, revenue, budgets, client contracts\n\nWhen finance_transparency: 1 (OPTIONAL):\n✅ CAN share: Project budgets, payment milestones, scope constraints (when contextually relevant)\n❌ STILL DON'T share: Individual rates, profit margins, full contracts, client's financials" }, { "title": "✅ ALWAYS OK to Share:", "body": "Project requirements and technical details\nTask assignments and deadlines\nTeam coordination information\nGeneral project status and priority\nTechnical support and guidance" }, { "title": "Example Daily Workflow", "body": "08:00 UTC - Send personalized status requests to 12 team members via Slack DMs\n\n10:00 UTC - Check Slack responses:\n\n2 responded → Ask for task IDs, update Obsidian\n10 no response → Send mid-day reminder\n\n14:00 UTC - Check again:\n\n5 more responded → Follow up, update tracking\n5 still pending → Note as delayed\n\n17:00 UTC - EOD check:\n\n8 total responded\n4 non-responders → Send EOD reminder, flag for next day\n\n18:00 UTC - Final tracking update:\n\nDocument response rates\nNote behavioral patterns\nPlan next day's approach\nKeep all internal notes confidential" }, { "title": "Integration with Obsidian", "body": "Create this structure in your PKM:\n\n# /root/life/pkm/daily-status/\n\n## README.md\n- Confidentiality rules\n- Process guidelines\n- Response benchmarks\n\n## YYYY-MM-DD/\n### TEAM STATUS - YYYY-MM-DD.md\nIndividual tracking per person:\n- Response time\n- Quality assessment\n- Behavioral notes\n- Project updates\n- Action items\n\n### SUMMARY.md\n- Overall response rate\n- Key observations\n- Critical non-responders\n- Next steps" }, { "title": "Slack API (via Maton Gateway)", "body": "# List users\ncurl -X GET \"https://gateway.maton.ai/slack/api/users.list\" \\\n -H \"Authorization: Bearer $MATON_API_KEY\"\n\n# Send DM\ncurl -X POST \"https://gateway.maton.ai/slack/api/chat.postMessage\" \\\n -H \"Authorization: Bearer $MATON_API_KEY\" \\\n -d '{\"channel\": \"USER_ID\", \"text\": \"Message\"}'\n\n# Get conversation history\ncurl -X GET \"https://gateway.maton.ai/slack/api/conversations.history?channel=CHANNEL_ID\" \\\n -H \"Authorization: Bearer $MATON_API_KEY\"" }, { "title": "Obsidian Skills", "body": "Use the obsidian skill to create and update daily tracking notes automatically." }, { "title": "Success Metrics", "body": "Response rate > 80% within 6 hours\nAverage response time < 3 hours\nClear task IDs and timelines provided\nBlockers identified early\nProactive communication increasing over time" }, { "title": "Lessons Learned", "body": "Personalization matters: Generic messages get ignored, specific project questions get responses\nConfidentiality is critical: Never share commercial/payment info with resources\nMultiple nudges work: Mid-day + EOD reminders significantly improve response rates\nDocument behavior: Patterns emerge over time, useful for resource management\nPrivate DMs only: Public status requests create comparison anxiety\nAsk for specifics: \"Making progress\" is useless, \"Task ID #123, 70% done, due Friday\" is actionable" }, { "title": "Related Skills", "body": "slack - Slack integration for messaging\nobsidian - PKM system for tracking notes\nteam-management - Broader team management approaches" }, { "title": "Version History", "body": "1.0.0 (2026-02-27) - Initial version with Slack + Obsidian integration, confidentiality rules\n\nAuthor: Real-world team status tracking implementation\nLicense: MIT\nTags: slack, team-management, status-tracking, obsidian, confidentiality" } ], "body": "Team Status Tracker via Slack\nOverview\n\nSystematic approach to track team member status updates via Slack DMs with Obsidian-based internal tracking. Maintains confidentiality while gathering actionable project updates.\n\nWhen to Use\nDaily/weekly team status check-ins\nProject progress monitoring\nResource management and workload tracking\nIdentifying blockers and support needs\nBehavioral pattern analysis for team optimization\nKey Principles\nCommunication (Slack DMs)\n\n✅ DO:\n\nSend personalized status requests (1-on-1 DMs)\nAsk specific questions about THEIR projects only\nRequest task IDs, timelines, specific blockers\nMaintain professional, supportive tone\nOffer help with blockers\nFollow up with non-responders (mid-day, EOD)\n\n❌ DON'T:\n\nShare financial information with resources (unless finance_transparency: 1 - see Configuration)\nShare billing amounts, revenue figures, client contracts (unless explicitly enabled)\nDiscuss other team members' performance publicly\nShare behavioral tracking notes with team (NEVER - always confidential)\nUse public channels for status requests (keep it private)\nInternal Tracking (Obsidian)\n\n✅ Track (Confidential):\n\nResponse times (prompt, delayed, no response)\nResponse quality (detailed, vague, minimal)\nBehavioral patterns (proactive, reactive, non-responsive)\nCommunication effectiveness\nBlockers and support needs\n\n❌ Never Share with Team:\n\nThese tracking notes\nPerformance comparisons\nResponse time metrics\nNon-responder lists\nConfiguration\nconfig.yaml\n\nCreate a configuration file at .openclaw/workspace/skills/team-status-tracker/config.yaml:\n\n# Team Status Tracker Configuration\n\n# Confidentiality Settings\nconfidentiality:\n # Financial information transparency\n # 0 = NEVER share financial info (billing, revenue, payments) with resources (DEFAULT)\n # 1 = Share financial context when needed (budget, project value, payment status)\n finance_transparency: 0\n \n # What to NEVER share regardless of transparency setting\n always_confidential:\n - Performance comparisons between team members\n - Behavioral tracking notes\n - Response time metrics\n - Non-responder lists\n - Internal strategy discussions\n\n# Slack Settings\nslack:\n check_interval_hours: 2 # How often to check for responses\n reminder_midday: true # Send mid-day reminder to non-responders\n reminder_eod: true # Send end-of-day reminder\n \n# Response Grading\nresponse_grading:\n excellent: \"<1h\"\n good: \"1-3h\"\n acceptable: \"3-6h\"\n delayed: \"6-12h\"\n poor: \">12h\"\n\nUsing the Config\n\nWhen finance_transparency: 0 (DEFAULT - Recommended):\n\n❌ DON'T share:\n\n\"This project is worth $50K\"\n\"Client is paying us $X/month\"\n\"You'll get paid when invoice clears\"\n\"Project budget is $XXX\"\n\"Client owes us money\"\n\n✅ DO share:\n\n\"This project is high priority\"\n\"Client needs this urgently\"\n\"This is a strategic client\"\nGeneral project scope and timeline\n\nWhen finance_transparency: 1 (Optional - Use with caution):\n\n✅ CAN share when contextually relevant:\n\n\"This project has a budget of $X - keep scope tight\"\n\"Client pays milestone-based, need to deliver by [date] for payment\"\n\"High-value client ($XX/month) - prioritize their requests\"\n\"We're waiting on client payment before next phase\"\n\n❌ STILL DON'T share:\n\nIndividual team member salaries or rates\nPerformance comparisons\nBehavioral tracking notes\nFull contract terms\nClient's internal budget/financials\nWhen to Enable Finance Transparency\n\nConsider finance_transparency: 1 when:\n\n✅ Working with senior team members (leads, managers)\n✅ Team owns P&L responsibility\n✅ Budget constraints affect decisions\n✅ Payment delays impact work planning\n✅ Team needs context for scope/priority decisions\n\nKeep finance_transparency: 0 when:\n\n✅ Junior team members (default safe option)\n✅ Contractors/outsourced resources\n✅ Large team with varied seniority\n✅ Uncertain about team maturity\n✅ Company policy requires strict separation\nMessage Examples by Config\n\nScenario: Team member asks about project priority/urgency\n\nWith finance_transparency: 0 (DEFAULT):\n\nThis is a strategic client for us - high priority.\nPlease prioritize their requests and maintain quality.\nLet me know if you need any support!\n\n\nWith finance_transparency: 1:\n\nThis is a high-value client ($X/month contract).\nProject budget is $Y - keep scope tight and deliver by [date].\nPayment is milestone-based, so meeting the deadline is critical.\nLet me know if scope creep becomes an issue!\n\n\nScenario: Team member asks why project is urgent\n\nWith finance_transparency: 0:\n\nClient needs this urgently for their Q1 launch.\nIt's a strategic partnership opportunity.\nCan you prioritize this over [other project]?\n\n\nWith finance_transparency: 1:\n\nClient needs this for Q1 launch - they've paid 50% upfront ($X).\nRemaining $Y comes on delivery by [date].\nCan you prioritize this? It's blocking our cash flow.\n\n\nScenario: Team member asks about changing scope\n\nWith finance_transparency: 0:\n\nLet's stick to the original scope for now.\nAny additions need client approval first.\nPlease document the request and I'll discuss with client.\n\n\nWith finance_transparency: 1:\n\nCurrent scope is fixed at $X - no room in budget.\nIf they want additions, we need to quote separately.\nPlease document the request with time estimate.\nI'll discuss pricing with client.\n\nProcess\n1. Morning: Send Status Requests\n\nSend personalized Slack DMs asking ONLY about specific person's projects:\n\nHi [Name]! 👋\n\nQuick status check on *[Their Project]*:\n\n📊 Could you please share:\n• Current progress this week?\n• Any blockers or challenges?\n• Coordination with team smooth?\n• Support needed?\n\nThanks! 🚀\n\n\nKey Rules:\n\n✅ Personalize for each person's actual projects\n✅ Ask specific questions\n❌ NO commercial/payment info\n❌ Don't mention other projects they're not on\n2. Throughout Day: Monitor & Respond\n\nCheck Slack every 2-3 hours:\n\nWhen someone responds:\n\nRead their response in Slack\nAsk follow-up questions via Slack:\nThanks for the update! 👍\n\nCould you provide:\n📋 Specific task ID or ticket number?\n📊 Current progress % or milestone?\n⏰ Expected completion date?\n🚧 Any blockers preventing progress?\n\nUpdate internal Obsidian tracking\nNever share confidential info in responses\n\nWhen no response by mid-day:\n\nHi [Name]! 👋\n\nJust a friendly reminder - still waiting for your status update.\n\nWould appreciate a quick response when you get a chance. Thanks! 🙏\n\n3. End of Day: Final Nudge\n\nFor non-responders:\n\nHi [Name]! ⏰\n\nQuick reminder - please share your status update by end of day today.\n\nThis helps us track progress and provide support. Thanks! 🙏\n\n4. Track in Obsidian (Internal Only)\n\nCreate daily tracking files:\n\ndaily-status/\n├── YYYY-MM-DD/\n│ ├── TEAM STATUS - YYYY-MM-DD.md\n│ └── SUMMARY.md\n└── README.md (confidentiality rules)\n\n\nTrack for each person:\n\nResponse time\nResponse quality\nBehavioral pattern\nProject updates\nBlockers mentioned\nFollow-up needed\nResponse Time Benchmarks\nExcellent: < 1 hour\nGood: 1-3 hours\nAcceptable: 3-6 hours (same day)\nDelayed: 6-12 hours\nPoor: > 12 hours or no response\nBehavioral Categories\n🟢 Proactive\nResponds quickly\nProvides detailed updates\nAnticipates questions\nAsks for clarification when needed\n🟡 Reactive\nResponds when prompted\nBasic updates provided\nNeeds follow-up questions\n🔴 Non-Responsive\nDelayed or no responses\nVague or incomplete updates\nRequires multiple nudges\nConfidentiality Rules\n🚫 ALWAYS CONFIDENTIAL (Regardless of Config):\nPerformance comparisons between team members\nBehavioral tracking notes\nResponse time metrics\nNon-responder lists\nInternal strategy discussions\n💰 FINANCIAL INFO (Config-Dependent):\n\nWhen finance_transparency: 0 (DEFAULT): ❌ DON'T share: Payment amounts, billing, revenue, budgets, client contracts\n\nWhen finance_transparency: 1 (OPTIONAL): ✅ CAN share: Project budgets, payment milestones, scope constraints (when contextually relevant) ❌ STILL DON'T share: Individual rates, profit margins, full contracts, client's financials\n\n✅ ALWAYS OK to Share:\nProject requirements and technical details\nTask assignments and deadlines\nTeam coordination information\nGeneral project status and priority\nTechnical support and guidance\nExample Daily Workflow\n\n08:00 UTC - Send personalized status requests to 12 team members via Slack DMs\n\n10:00 UTC - Check Slack responses:\n\n2 responded → Ask for task IDs, update Obsidian\n10 no response → Send mid-day reminder\n\n14:00 UTC - Check again:\n\n5 more responded → Follow up, update tracking\n5 still pending → Note as delayed\n\n17:00 UTC - EOD check:\n\n8 total responded\n4 non-responders → Send EOD reminder, flag for next day\n\n18:00 UTC - Final tracking update:\n\nDocument response rates\nNote behavioral patterns\nPlan next day's approach\nKeep all internal notes confidential\nIntegration with Obsidian\n\nCreate this structure in your PKM:\n\n# /root/life/pkm/daily-status/\n\n## README.md\n- Confidentiality rules\n- Process guidelines\n- Response benchmarks\n\n## YYYY-MM-DD/\n### TEAM STATUS - YYYY-MM-DD.md\nIndividual tracking per person:\n- Response time\n- Quality assessment\n- Behavioral notes\n- Project updates\n- Action items\n\n### SUMMARY.md\n- Overall response rate\n- Key observations\n- Critical non-responders\n- Next steps\n\nTools Integration\nSlack API (via Maton Gateway)\n# List users\ncurl -X GET \"https://gateway.maton.ai/slack/api/users.list\" \\\n -H \"Authorization: Bearer $MATON_API_KEY\"\n\n# Send DM\ncurl -X POST \"https://gateway.maton.ai/slack/api/chat.postMessage\" \\\n -H \"Authorization: Bearer $MATON_API_KEY\" \\\n -d '{\"channel\": \"USER_ID\", \"text\": \"Message\"}'\n\n# Get conversation history\ncurl -X GET \"https://gateway.maton.ai/slack/api/conversations.history?channel=CHANNEL_ID\" \\\n -H \"Authorization: Bearer $MATON_API_KEY\"\n\nObsidian Skills\n\nUse the obsidian skill to create and update daily tracking notes automatically.\n\nSuccess Metrics\nResponse rate > 80% within 6 hours\nAverage response time < 3 hours\nClear task IDs and timelines provided\nBlockers identified early\nProactive communication increasing over time\nLessons Learned\nPersonalization matters: Generic messages get ignored, specific project questions get responses\nConfidentiality is critical: Never share commercial/payment info with resources\nMultiple nudges work: Mid-day + EOD reminders significantly improve response rates\nDocument behavior: Patterns emerge over time, useful for resource management\nPrivate DMs only: Public status requests create comparison anxiety\nAsk for specifics: \"Making progress\" is useless, \"Task ID #123, 70% done, due Friday\" is actionable\nRelated Skills\nslack - Slack integration for messaging\nobsidian - PKM system for tracking notes\nteam-management - Broader team management approaches\nVersion History\n1.0.0 (2026-02-27) - Initial version with Slack + Obsidian integration, confidentiality rules\n\nAuthor: Real-world team status tracking implementation License: MIT Tags: slack, team-management, status-tracking, obsidian, confidentiality" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/parthpandya1729/team-status-tracker", "publisherUrl": "https://clawhub.ai/parthpandya1729/team-status-tracker", "owner": "parthpandya1729", "version": "1.0.3", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/team-status-tracker", "downloadUrl": "https://openagent3.xyz/downloads/team-status-tracker", "agentUrl": "https://openagent3.xyz/skills/team-status-tracker/agent", "manifestUrl": "https://openagent3.xyz/skills/team-status-tracker/agent.json", "briefUrl": "https://openagent3.xyz/skills/team-status-tracker/agent.md" } }