MacHu-GWU/sqlalchemy_upsert_kit-project / .claude/skills/pywf-oss-setup-machine
pywf-oss-setup-machine
VerifiedGuide the maintainer through setting up a Mac for pywf open-source Python libraries: global mise, uv and gh, shell activation, the home_secret.toml key paths, and the GitHub, Codecov, Read the Docs and PyPI tokens, verified without printing any secret. Use when the user sets up a new machine, asks how the environment works, rotates a token, or a task fails for a missing tool or token.
Take a machine from nothing to "every template repo runs mise run inst, and every setup task finds its token", as a guided runbook: check, report, and leave every step that touches a secret to the user.
Read ../pywf-oss-base/SKILL.md, then:
- ../pywf-oss-base/references/01-secrets.md
- ../pywf-oss-base/references/02-machine-setup.md
Steps
- Check the tools:
mise --version,uv --version,gh auth status, andmise activatein~/.zshrc. Report what is present and missing in a short table. - Install what is missing. Show the
brew install ...lines, and run them after the user's yes.gh auth loginis interactive; run it only if the user asks. - Secrets file.
- Check only that the file exists and its permissions, with
ls -l ~/home_secret.toml. Never read its content. - If it is missing, list the key paths in the
[env]block ofmise.toml, say what each value is for, and show thechmod 600line.
- Check only that the file exists and its permissions, with
- Tokens. For each token, give the creation URL and the exact scopes. The user creates each token and writes it into the file. Never ask for a token in the chat.
- Verify. In a template repo, run
mise trustif needed, thenmise run instand the True/False check. Report each variable as present or missing, naming themise.tomlkey path of a missing one.
Boundaries
- The user makes account-level settings, such as connecting GitHub in Read the Docs, in the browser. Give the link and say what to click.
Next step for a new repo: pywf-oss-setup-repo.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |