← Back to Skills Marketplace
Team Status Tracker
by
parthpandya1729
· GitHub ↗
· v1.0.3
380
Downloads
0
Stars
2
Active Installs
4
Versions
Install in OpenClaw
/install team-status-tracker
Description
Systematic team status tracking via Slack DMs with confidential Obsidian-based internal tracking. Maintains confidentiality while gathering actionable projec...
Usage Guidance
Key points to check before installing/using:
- Credentials & dependencies: The skill itself declares no Slack or Obsidian credentials; it depends on other skills to provide those. Confirm which 'slack' and 'obsidian' skills will be used, where they store tokens, and who can access them.
- Filesystem defaults: The provided config/template defaults point at /root and .openclaw workspace paths. Change obsidian_path to a safe, intended directory in your user workspace and confirm permissions before storing confidential notes.
- Privacy & consent: The templates encourage confidential behavioral tracking and non-responder lists. Ensure this matches your company policies and legal/Human Resources guidance — covert tracking of staff can be legally and ethically problematic.
- Automation scope: Because the instructions describe automated checks and reminders, make sure automation is explicit, rate-limited, and tested in a non-production environment to avoid spamming team members.
- Audit other skills: Review the 'slack' and 'obsidian' skills that will be used in conjunction with this one. The real security/privilege footprint (message sending, file writes, credential storage) lives with those skills, not this instruction-only package.
If you proceed, sanitize default paths, set conservative retention (or manual purge), require explicit consent for behavioral notes, and test in a sandboxed workspace first.
Capability Analysis
Type: OpenClaw Skill
Name: team-status-tracker
Version: 1.0.3
This skill is classified as benign. It is designed for systematic team status tracking via Slack DMs and confidential Obsidian-based internal tracking. The documentation (SKILL.md, README.md, templates) consistently and emphatically instructs the AI agent to maintain strict confidentiality, explicitly forbidding the sharing of financial information, performance comparisons, behavioral tracking notes, and other sensitive data with team members. While the skill involves collecting sensitive 'behavioral patterns' and requires network (Slack API via Maton Gateway) and local file system access (Obsidian), these capabilities are necessary for its stated purpose, and the instructions are overwhelmingly focused on ethical and confidential data handling, rather than misuse or exfiltration. There is no evidence of malicious execution, persistence mechanisms, obfuscation, or prompt injection attempts designed to subvert the agent's intended behavior.
Capability Assessment
Purpose & Capability
The skill claims Slack and Obsidian integration and the SKILL.md metadata lists required skills ['slack','obsidian'], which explains why it itself doesn't list Slack tokens. However, the skill does not declare any credentials or explicitly state how Slack/Obsidian access is provided. It also hardcodes an absolute default obsidian_path (/root/life/pkm/daily-status) which is unexpected for a general-purpose skill and may not be appropriate for most users. Overall plausible but under-specified.
Instruction Scope
The instructions tell the agent/operator to send personalized Slack DMs, monitor replies, follow up, and maintain confidential behavioral-tracking notes in Obsidian. They explicitly instruct creating and persisting files, documenting non-responders and behavioral observations, and include templates for automated reminders. That scope goes beyond a benign 'status template' helper: it instructs ongoing monitoring and storage of potentially sensitive personnel behavior data. It also references writing to .openclaw/workspace and to an absolute /root path—actions that require filesystem access and could produce long-lived private records.
Install Mechanism
Instruction-only skill with no install spec and no code files to execute. This minimizes direct installation risk—nothing in the bundle downloads or executes external binaries. The runtime behavior depends on other installed skills (slack, obsidian).
Credentials
The skill requests no environment variables or credentials itself, which is consistent with being an instruction-only wrapper that expects 'slack' and 'obsidian' skills to provide access. However, the included default config and templates use absolute filesystem paths (e.g., /root/...) and specify retention policies (keep_history_days: 90). Those defaults are disproportionate if applied without review because they assume write access to top-level filesystem locations and long-lived storage of sensitive behavioral data. Also, because the skill expects Slack automation, verify where Slack tokens will be stored and which skill will actually send messages.
Persistence & Privilege
always:false and no install components — the skill does not force permanent inclusion. However, the instructions assume the agent (or other skills) will autonomously send periodic reminders and write tracking files. If the agent is allowed to invoke skills autonomously, this could result in continuous monitoring/DMing. Consider the automation policy and consent implications before enabling autonomous runs.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install team-status-tracker - After installation, invoke the skill by name or use
/team-status-tracker - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.3
No changes detected in this version.
- Version 1.0.3 does not introduce any new features, updates, or fixes.
- All files remain unchanged from the previous release.
v1.0.2
Added configurable finance_transparency flag (0=never share financial info, 1=share budget/payment context). Includes config.yaml template, message examples for both settings, and guidance on when to enable transparency.
v1.0.1
Security update: Removed all sensitive company/team/project information from examples
v1.0.0
Initial release: Slack DM status tracking with Obsidian integration, confidentiality rules, behavioral pattern tracking
Metadata
Frequently Asked Questions
What is Team Status Tracker?
Systematic team status tracking via Slack DMs with confidential Obsidian-based internal tracking. Maintains confidentiality while gathering actionable projec... It is an AI Agent Skill for Claude Code / OpenClaw, with 380 downloads so far.
How do I install Team Status Tracker?
Run "/install team-status-tracker" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Team Status Tracker free?
Yes, Team Status Tracker is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Team Status Tracker support?
Team Status Tracker is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Team Status Tracker?
It is built and maintained by parthpandya1729 (@parthpandya1729); the current version is v1.0.3.
More Skills