Overnight Factory

Set up an AI agent as an Overnight Software Factory operator. Use when configuring an OpenClaw agent to autonomously handle support tickets end-to-end: recei...

This skill appears to implement the ticket→PR automation it advertises, but exercise caution before installing. Key concerns: - The skill metadata lists no required env vars, but the instructions require GITHUB_TOKEN, EMAIL_USER, and EMAIL_PASSWORD — confirm what secrets you must provide. - The SKILL.md tells you to store your GitHub token in ~/.git-credentials and set global git user/email. That persists a token in plaintext and affects all git activity on the machine; prefer a least-privilege approach (repo-scoped deploy keys or fine-scoped personal access tokens) and avoid writing tokens to global files. - It instructs running Claude Code with --dangerously-skip-permissions, which disables local permission checks. Avoid this or understand exactly what permissions are being bypassed. - The cron + subagent design gives the skill ongoing autonomous power to clone repos, commit, push, and open PRs. Test everything in a limited/staging environment and use a bot account with minimal scopes (only the repos and actions it truly needs). Rotate tokens regularly and monitor audit logs. - Before going live, verify exactly which files the skill will write (memory/, workspace/, ~/.git-credentials) and consider isolating the agent on a dedicated account or container. If you want to proceed: create a constrained bot account with minimal scopes, avoid storing tokens in global git files, don't use --dangerously-skip-permissions, and run the cron in a controlled/staging environment first.

Type: OpenClaw Skill Name: overnight-factory Version: 1.0.0 The skill bundle configures an autonomous 'Software Factory' with high-risk capabilities, including the use of the `--dangerously-skip-permissions` flag for Claude Code and the storage of sensitive credentials (GitHub tokens and email passwords) in plain text via `.env` and `~/.git-credentials`. While these actions are aligned with the stated goal of autonomous ticket handling, the instructions in SKILL.md and references/ticket-pipeline.md create a significant security risk by bypassing execution safeguards and exposing secrets in the filesystem and git configurations. No clear evidence of intentional data exfiltration or malicious intent was found, but the configuration is inherently insecure.