Glean 拾遗
Daily · timeline

A few picks a day.

Sun, Nov 15, 2026 3picks
← 11-14
Calendar ▾
2026 · 11
MoTuWeThFrSaSu ······123456789101112131415161718192021222324252627282930
has picks today
11-16 →
06:00

Cursor's plugin spec and official plugin catalog for agent skills

Cursor 官方插件规范与插件库:把 agent 能力封装成可复用单元

A Cursor-maintained plugin specification plus a catalog of official plugins. Each plugin is described by a plugin.json manifest (name, author, category) and bundles skills, commands, scripts, or connectors into units an agent can invoke directly. The collection splits into two halves: developer-workflow plugins (PR review canvases, parallel subagent orchestration, CLI patterns agents can run reliably, scaffolding and validation via create-plugin) and integrations that expose external systems such as GitHub, Playwright, BigQuery, Salesforce and Gmail to the agent. Useful if you are packaging reusable capabilities for coding agents, or want a reference for how the vendor structures and distributes them.

github.com · 15 min · Agent Skills · Cursor · Developer Tools · Mcp · Plugin System
06:00

Your Coding Agents Made You a Manager

带 agent 写代码,本质是在做管理

Addy Osmani maps engineering-management practice onto day-to-day coding-agent work: give the agent a definitive pass/fail check (tests, build exit codes, screenshots) instead of accepting "looks done"; write down only the context the repo cannot reveal — objective, constraints, out-of-scope items, success criteria; and once you have corrected the same thing twice, put it in CLAUDE.md or a shared skill. He borrows Grove's task-relevant maturity to explain Claude Code's split between requests (prompts, CLAUDE.md, skills) and requirements (hooks, deny rules, managed settings), arguing that over-process is the new micromanagement. The piece also lists five questions to answer before an unattended run, and is candid about where the analogy breaks: agents have a notebook rather than experience, rework is nearly free, and the human team still needs your time.

06:00

The five primitives behind always-on agents

常驻 Agent 的五个原语:收件箱、定时器、记忆、权限与发件箱

Always-on agents are mostly asleep: an event wakes a worker, a short run executes, state is written back, and the agent sleeps again. The post decomposes the surrounding architecture into five primitives. An event inbox (durable table + handler + worker) replaces letting each event source call the agent directly, avoiding competing runs and lost events on crash. Timers split into agent-set follow-ups and recurring schedules, stored separately and fired by a polling scheduler that writes into the inbox. Memory is a directory of files for user instructions, user notes, past messages and task progress, with the rule that memory only holds what cannot be looked up elsewhere. Permissions rely on a credential-injecting proxy, classifier-based auto mode, and deferred tool calls that end a run mid-call and resume it from a new event. An outbox with a dispatcher paces delivery and enables retries. The only hard number is a 78% per-task cost drop on a long-horizon coding benchmark versus 40% on typical workloads.