headlesson_feedback
ClaudeThis content is sent to the headlesson operator. Feedback about headlesson itself is sufficient. Do not include personal information or conversation contents.
Developer-Tools
Overview
headlesson is a catalog of command-line tools, MCP servers and APIs for agents. Most records include the install, check and first-task steps that the headlesson operator ran, the dated result (passed, partial, failed or untested) with the version and environment, and known failure conditions — for example a PDF tool that exits 0 but returns empty text. Use it when you are choosing or comparing a tool for a task such as extracting text from PDFs, filtering JSON, searching code or resizing images; before installing or connecting a tool; when a tool succeeds but its output looks wrong; or when you need to know what changed in agent tools after a date. Tools: headlesson_search (find and compare by task, product name or facts such as auth, pricing and license), headlesson_get (one record with steps, results, pitfalls and sources), headlesson_whats_new (dated changes since a date), headlesson_feedback (send a short note to the operator; it is stored and is not published). Records state their source and check date. A recorded result is an observation on one machine at one version, not a guarantee of how a tool behaves elsewhere or of its safety. When no curated record matches, one public word from the query may be looked up in the Official MCP Registry; those listings are unverified.
Tools
headlesson_get
ClaudeGet one record by an ID from headlesson_search: an app, usecase, feature, concept or change. For an app, sections ["lesson","gotchas"] return the install, check and first-task steps with the recorded test result (a dated observation by the headlesson operator) and known failure conditions; "relations" lists alternatives and what it wraps or depends on; "axes" returns every compared fact. Without sections you get the description, interfaces and six main axes. Each fact carries its source and check date; private sources appear as labels, not links. Official MCP Registry listing IDs are fetched live and are unverified; a failed lookup does not prove the ID absent.
headlesson_search
ClaudeFind command-line tools, MCP servers and APIs for a task, and compare them. Ask in plain English or Japanese ("extract text from scanned PDFs") or by product name. Each result gives an ID, a one-line reason it matches, and when it was checked. Pass the ID to headlesson_get with sections ["lesson","gotchas"] to get the steps (install, check, first task) with their recorded test result (most were run by an agent; a few are untested) and known failure conditions, such as a tool that exits 0 with empty or wrong output. Filter or compare with axes such as auth, pricing, license and remote_mcp (where, axes, ids). Curated records come first. If none match, or include:["registry"] is set, one public word from the query is looked up in the Official MCP Registry; those listings are unverified (what is sent is described on the query field).
headlesson_whats_new
ClaudeList dated changes in agent tools and standards (new tools, renames, deprecations, breaking changes, new standards) since a date, optionally by kind or affected record. Useful for checking what changed after your training data. Public source URLs are kept; private sources appear as labels.
Links
App Stats
4
Tools
Claude
Platforms
Category
Technical Knowledge SearchWorks with
Claude
Similar Apps
Data refreshed daily