# Operate Local Project Stacks Safely

Local development stacks can be hard to debug when logs, services, and config changes are handled out of order. This skill guides Claude, Codex, and Claude Code to inspect evidence first and explain safe operational steps.

## Install

```bash
npx skillstore add acskamloops/project-operator
```

## Metadata

- Status: approved
- Slug: acskamloops-project-operator
- Skillstore revision: r1
- Version status: missing
- Tree hash: 74dd021c87c8fb859325d6115f2449f7792963b3cd0392cd1c1e59186f25260f
- Author: ACSKamloops
- GitHub username: ACSKamloops
- License: MIT
- Repository: https://github.com/ACSKamloops/shs-engine/tree/master/.codex/skills/project-operator
- Ref: c1fdca50ff516318f65fed0d7f9e82797c5171dc
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/acskamloops-project-operator
- Manifest: https://skillstore.pages.dev/api/skills/acskamloops-project-operator/manifest

## Capabilities

- Guides local API, worker, and frontend troubleshooting with an observability-first approach.
- Prioritizes logs and status endpoints before service restarts.
- Encourages incremental changes that protect uptime and clarity.
- Requests plain-language impact notes and revert paths for config changes.
- Prompts stop or cancel strategies for long-running commands.

## Use Cases

- Troubleshoot Local Services: Inspect local API, worker, and frontend behavior by checking logs and status signals before changing services.
- Review Config Changes: Explain the operational impact of config updates and document a clear rollback path before applying them.
- Plan Safe Automation: Prepare incremental operational steps with observable checkpoints and stop strategies for long-running commands.

## Prompt Templates

### Check Stack Health

```
Use project-operator to inspect the local API, worker, and frontend health. Start with logs and status endpoints. Summarize findings and next steps.
```

### Debug One Failing Service

```
Use project-operator to debug the failing local service. Read recent logs first, identify likely causes, and suggest the smallest observable fix.
```

### Assess a Config Change

```
Use project-operator to review this config change. Explain impact in plain language, list risks, and provide a practical revert path.
```

### Coordinate a Long Operation

```
Use project-operator to plan this long-running operation. Define checkpoints, observability signals, stop criteria, and a cancel strategy before execution.
```

## Limitations

- Does not include executable scripts, command wrappers, or automation code.
- Does not define specific service names, ports, providers, or deployment targets.
- Requires project context before recommending exact operational actions.
- Does not replace production monitoring, access controls, or incident response processes.

## Best Practices

- Check logs and status endpoints before restarting local processes.
- Make operational changes incrementally and verify each result.
- Document config impact and a rollback path before applying changes.

## Anti Patterns

- Restarting services before collecting evidence from logs or health checks.
- Changing multiple configuration values without a clear verification point.
- Running long commands without stop criteria or a cancel strategy.

## Security Audit

- Audited at: 2026-07-06T00:28:33.005\+00:00
- Summary: No static findings were reported for this prompt-only skill. Review of SKILL.md found operational safety guidance and no prompt-injection language, executable code, network behavior, or data-exfiltration intent.

## Stats

- Views: 210
- Downloads: 10
- Favorites: 0
- Popularity score: 0