michael-f-bryan/working-docs
skills/working-docs/SKILL.md
Use when handling multi-step tasks, investigations, or long sessions where working notes, interim findings, and scratch planning are needed to keep context and handoffs clear.
documentation
Updated May 21, 2026
$ install --global
skillsauthnpx skillsauth add michael-f-bryan/skills working-docsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 21, 2026, 6:57 AM147.9s1 file scanned
SKILL.md
- name:
- working-docs
- description:
- Use when handling multi-step tasks, investigations, or long sessions where working notes, interim findings, and scratch planning are needed to keep context and handoffs clear.
The _working/ directory is a scratch space purely for your use.
When to use
- Multi-step implementation, debugging, or investigation work.
- Tasks likely to span a long session or multiple handoffs.
- Cases where interim findings should be captured before final output.
When not to use
- One-shot requests that can be completed directly with no intermediate reasoning artifact.
- Final user-facing docs that belong in the repository outside
_working/.
Working notes convention
Use a stable path so notes are easy to find and continue:
_working/<topic>/notes.mdfor running notes and decisions_working/<topic>/scratch.mdfor temporary drafts/experiments
As you work through a problem, always write notes to _working/. Capture observations and the reasoning that connects those observations to the task or broader project. Keep notes structured so another agent (or a future session) can resume quickly.
You may delete files in the scratch space when you are done with them.
Related Skills
michael-f-bryan/wikilinks
documentation
VerifiedTrustedCommunity
When generating or editing markdown content, actively look for existing pages to link to and incorporate relevant wikilinks so content is interconnected. Use when writing notes, docs, or any .md content.
SKILL.mdUpdated May 21, 2026
michael-f-bryan/wait-for-ci
development
VerifiedTrustedCommunity
Wait for a GitHub Actions run to finish with minimal terminal output and a reliable exit code. Use when an agent must wait for CI to pass (e.g. after push, after opening a PR, or when verifying a specific run). Prefer gh run watch with --exit-status and --compact to avoid flooding context with poll output.
SKILL.mdUpdated May 21, 2026
michael-f-bryan/voice-michael
testing
VerifiedTrustedCommunity
Use when drafting, editing, or evaluating communication that should sound like Michael across public technical prose, internal notes, agent prompts, engineering feedback, and concise operational updates.
SKILL.mdUpdated May 21, 2026
michael-f-bryan/temporal-applications-python
development
VerifiedTrustedCommunity
Design, implement, and refactor high-quality Temporal workflows and activities in Python. Use when building or changing Temporal Python applications; when designing activities (injectable deps, Pydantic params/result, business logic outside); when implementing workflows with dynamic inputs or Continue-As-New; or when configuring reliability (timeouts, retries, idempotency), determinism, or testing. Covers boundaries, typed contracts, bounded history, and progressive disclosure via resources.
SKILL.mdUpdated May 21, 2026