| name | legible-operational-status-updates |
|---|---|
| description | Use whenever working on operational tasks, including deployments, cloud infrastructure, service configuration, migrations, incident response, and operational troubleshooting. Keep the user informed after every step and at least every three minutes while waiting for long-running tasks, using a consistent, legible status-update format. |
Keep the user informed about what has happened, the current operational state, and what happens next.
Paseo schedules start a fresh agent on each run. When that agent finishes, Paseo notifies you: an in-app notice if you are active in the app, or a push notification if you are away. As of Paseo 0.9.2 there is no per-schedule setting to turn this off.
This matters for:
This note describes a workaround. It relies on internal behaviour, so treat it as a hack that a future Paseo release may break.
Use this skill to encrypt a message or file with any GitHub user's public key.
The skill will then generate a gist (like this one) with the encrypted payload and instructions for their agent to decrypt it.
This gist contains the Hermes Agent dog skill.
Install by copying SKILL.md into a Hermes skill directory, for example:
mkdir -p ~/.hermes/skills/productivity/dog
curl -L <raw-SKILL.md-url> -o ~/.hermes/skills/productivity/dog/SKILL.md
mkdir -p ~/.hermes/skills/productivity/dog/references
| name | hermes |
|---|---|
| description | Send commands, questions, and work requests to a user-configured remote Hermes ACP agent over SSH, then return the complete acpx/Hermes output without summarizing. Use this skill whenever the user asks to talk to, ask, delegate to, or run work through their remote Hermes agent or always-on remote agent. Configure hostnames, session names, paths, and behavior with environment variables such as $REMOTE_HERMES_HOST and $REMOTE_HERMES_SESSION_NAME. |
| compatibility | Requires network access to $REMOTE_HERMES_HOST, SSH authentication for that host, Node/npm with npx or a global acpx install, and a working Hermes ACP command on the remote host. |
Use this skill to communicate with a user-configured remote Hermes agent through ACP over SSH.
Alex from Ramp Labs describes an experiment in making Ramp Sheets more self-maintaining by connecting background coding agents to production observability. The core shift is that AI has reduced the effort of writing code, so the bottleneck moves to maintenance, monitoring, triage, and directing agents at the right problems. Ramp's answer is not merely "an agent that codes", but a system where agents inspect live behaviour, create monitors, respond to alerts, tune noisy signals, and generate pull requests for real issues.
The talk begins with Ramp Labs' broader AI work, including Ramp Sheets, Latent Briefing, and steering vectors, but quickly centres on a practical problem: once AI can handle much of the coding, engineers spend more time deciding what needs attention.
"code maintenance"
Eric Zakariasson argues that agentic software work is moving from pair-programming toward managed production systems: developers increasingly define intent, constraints, feedback loops, and verification rather than writing every line themselves. Cursor is not fully at the "software factory" stage yet, but parts of its product and company already run with high autonomy, offering practical lessons for teams trying to build similar systems.
The talk frames AI coding progress as a climb through levels of autonomy:
In this AI Engineer talk, Ryan Lopopolo argues that modern coding agents change the scarce resource in software engineering. The bottleneck is no longer typing implementation code, but designing the systems, context, guardrails, review loops, and operating practices that let agents reliably do the full job. His core claim is that engineering teams should reorganise around delegation, systems thinking, context management, and automation of acceptance criteria, rather than treating agents as autocomplete or code-writing assistants.
"Code is free."
Lopopolo frames coding agents as a major shift in engineering economics: implementation is becoming abundant, while human time, human/model attention, and model context window remain scarce. Engineers now have access to the equivalent of many parallel implementers, limited mai
| tmp() { | |
| mkdir -p ~/.tmp | |
| # Cleanup directories older than 23 days | |
| find ~/.tmp -mindepth 1 -depth -Btime +23d -delete 2>/dev/null | |
| local timestamp=$(date +%Y-%m-%d-%H-%M-%S) | |
| local dir | |
| if [[ -n "$1" ]]; then |
| <instructions> | |
| Create a structured summary of <input />, scaled to approximately [num-pages] page(s) when rendered. | |
| ## Structure | |
| ### Title | |
| Start with a `##` heading that captures what is being summarised (e.g., the article title, report name, or a descriptive title you create). | |
| ### Opening Paragraph | |
| Immediately after the title, write a paragraph stating the core thesis or takeaway. No heading for this paragraph — just the prose. |