Monitors GitHub organization commits daily, providing team activity updates and current standings on demand via /team-status command.

Do not install or run this skill without resolving inconsistencies: (1) Inspect monitor.py fully to confirm it only calls GitHub APIs and does not contact any other endpoints. (2) Confirm which environment variables the code actually needs — the script currently reads GITHUB_TOKEN but hardcodes ORG/TEAM_SLUG; either update the script to read GITHUB_ORG/TEAM_SLUG from env or change the documentation. (3) Use a least-privilege GitHub token (prefer read-only scopes such as read:org and repo:status or a token scoped to read-only access for the needed repos) and preferably a machine/bot account, not a personal account with broad permissions. (4) Be aware sample_state.json contains commit metadata (emails, commit URLs) which may be sensitive; avoid publishing it. (5) If you plan to post outputs to chat channels, ensure that posting is done by a trusted integration and not baked into the script. If the author cannot explain the env/metadata mismatch or provide a version that reads configuration from environment variables securely, treat the skill as untrusted.

Type: OpenClaw Skill Name: github-tracker Version: 1.0.3 The skill is a GitHub activity tracker designed to monitor commit frequency for a specific organization team ('OpenPecha'). It retrieves commit metadata via the GitHub API using a provided GITHUB_TOKEN and maintains local state in 'state.json'. While there is a minor discrepancy between the documentation and the hardcoded organization name in 'scripts/monitor.py', and the use of future-dated metadata/API versions, the code performs legitimate API interactions without evidence of data exfiltration, prompt injection, or malicious execution.