fix: add mcporter skill + remove obsolete playwright references

[royosherove]

• Adds mcporter/SKILL.md to repo (was only at ~/.pi/agent/skills/, not synced on fresh setup)
• Removes playwright MCP server references (using playwright-cli direct CLI instead)
• Adds note directing users to playwright-cli skill for browser automation
• Cleans up examples to focus on 5 configured servers (aws-mcp, aws-knowledge, aws-documentation, aws-iac, aws-pricing)

[github-actions]

Claude finished @royosherove's task in 54s —— View job

---

PR Review

• Gather context
• Read changed files
• Analyze and provide review

---

Summary

This PR adds mcporter/SKILL.md — a well-structured reference doc for using MCP servers via the mcporter CLI. The file is clean, readable, and follows the same pattern as other skills in this repo. No functional code is introduced, so risk is low.

Overall: ✅ Looks good to merge.

---

Observations

Strengths:

• Clear Quick Reference section with concise CLI syntax
• Comprehensive usage examples across all 5 configured servers
• Practical tips section (JSON quoting, timeout env var, piping output)
• Good cross-reference to playwright-cli skill rather than duplicating browser automation guidance

Minor points to consider (non-blocking):

1. Hardcoded path reference (mcporter/SKILL.md:53):

   See `~/.pi/agent/skills/playwright-cli/SKILL.md`.
   

   This points to a local filesystem path (~/.pi/agent/skills/) that is installation-specific and may not match all users' setups. Consider referencing the skill by name or using a relative path within the repo (./playwright-cli/SKILL.md) instead, or simply omitting the absolute path. Fix this →

2. read_documentation URL in requests param (mcporter/SKILL.md:93):
   The example passes a real AWS docs URL. This is fine for documentation but worth noting that the URL could go stale over time. Not a blocker.

3. No frontmatter triggers field: Other skills in the repo may use additional frontmatter fields. This skill only has name and description, which appears consistent with the pattern here — no issue.