Your Name
2dabf8ef03
- memory/: cross-session project memory with decisions, lessons, failures, architecture, and sessions categories. Each has format templates and lifecycle documentation. - skills/: 12 reusable specialized methodologies (tdd, systematic-debugging, architecture-design, code-review, security-review, repository-analysis, failure-analysis, refactoring, test-analysis, incident-investigation, browser-automation, research). Each has frontmatter and methodology sections. - improvements/: proposal-based improvement system requiring human approval. - scripts/memory-lifecycle.sh: deterministic memory operations (recall, store, list, search, sessions, cleanup). - scripts/test-memory-system.sh: 12 structural tests for all new systems. - orchestrator.md: added Memory Recall stage, Learning and Memory Storage stage, Improvement Proposals workflow, memory/skills rules, and 3 new actions (A23-A27) to the action catalog. Updated behavioral acceptance test and state separation model. - All 12 subagents: added Memory & Skills Awareness sections with recall and store instructions. - docs/AGENT_ARCHITECTURE.md: documented memory, skills, and improvements systems (sections 12-14). Updated action count (27), state model, and remaining weaknesses. - README.md: documented new systems, updated repository layout, added test-memory-system.sh documentation. All 39 tests pass (16 architecture + 12 memory + 11 bootstrap).
1.1 KiB
1.1 KiB
name, description, version, owner, prerequisites
| name | description | version | owner | prerequisites |
|---|---|---|---|---|
| browser-automation | Browser automation patterns — web interaction, scraping, and testing | 1.0 | Explorer | web technology available, target URL known |
Browser Automation
When to use this skill
- Web content needs to be fetched and analyzed
- UI behavior needs to be verified
- API documentation needs to be read from web sources
Core methodology
IDENTIFY TARGET → SELECT TOOL → FETCH/INTERACT → ANALYZE → RECORD
Patterns
Content fetching
- Use
webfetchtool for static content - Prefer markdown format for readability
- Handle errors and timeouts gracefully
Research
- Use
websearchfor finding information - Use
webfetchfor reading specific pages - Cite sources with URLs
Verification
- Fetch expected content
- Compare with actual behavior
- Document discrepancies
Common pitfalls
- Assuming content hasn't changed since last fetch
- Not handling rate limits
- Fetching more than needed (context bloat)
- Trusting web content without verification
Exit criteria
- Content fetched and analyzed
- Sources cited
- Findings recorded