passo.uno valid
Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.
Manage this listing — optional · Visit publisher ↗
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for passo.uno:
1. POST https://agentwebmap.com/v1/sites/passo.uno/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://passo.uno/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/passo.uno/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/passo.uno).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory. Ownership management is optional.
passo.uno
Technical writing, AI, and docs engineering by Fabrizio Ferri Benedetti.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-21T06:03:14.958Z. Cached copy · Source on passo.uno
# passo.uno
> Technical writing, AI, and docs engineering by Fabrizio Ferri Benedetti.
I’m Fabrizio Ferri Benedetti, a technical, UX, and programmer writer based in Barcelona, Spain. I write and explore tech for a living. I’ve been communicating about tech and connecting people at tech companies since 2008, first as a content strategist, then as an API designer and tech writer.
I know enough coding to be dangerous and I often create my own tools. I love the Oxford comma, em dashes, semicolons, and the interrobang. My grammar is descriptive when writing and prescriptive when editing. I break rules all the time if it helps getting a message across.
## Posts
- [Tech needs humanists more than ever](https://passo.uno/tech-needs-humanists-more-than-ever/index.md): Whoever speaks badly, thinks badly and lives badly. We must find the right words: words are important! —Nanni Moretti
A reader reached out to me the other day to talk about the future of tech writing as a profession. They asked me a pretty good question: What skills would you prioritize in this age of constant change and uncertainty? Is it AI? Maybe coding? Well, not really.
- [Does whispering to agents in docs help?](https://passo.uno/if-you-are-an-agent-read-this/index.md): I’m seeing more instances of docs and README files addressing agents directly, as in “Hey, if you’re an agent, follow these instructions”. In some cases, those instructions are visible to human readers as well, which makes for a deeply awkward experience, the reading equivalent of getting a robotic kick in the butt. Is this whistling to machines helpful? I ran some experiments to find out.
- [Advice for tech writers on a job hunt in the AI age](https://passo.uno/job-hunt-tech-writers-ai/index.md): A friend of mine recently lost her job in a layoff. She looked at her résumé with a pang of despair and asked me for advice on what she should learn next. She hasn’t thrown in the towel on technical writing yet; she wants to find another tech writing job, despite the prevailing pessimism that besieges our craft. How does one upgrade to, say, content engineering, she asked.
- [You can write in LLMese, but you don’t have to](https://passo.uno/write-docs-llms-language/index.md): While chatting with Sarah Deaton about the formats agents could use to talk to each other, we got to questions that might sound obvious: why should machines (say, LLMs) communicate with each other like we do? Do they need all the rhetoric we carry around? Or could they get by with a terser register, one that carries the same meaning but in far fewer tokens?
- [Feed the machines, then guide the humans](https://passo.uno/tech-writing-role-split/index.md): Docs as code used to mean editing docs as if they were code. Today it also means that docs have become executable, either as agentic instructions, skills, or context for large language models. Tech writers must now ensure that the reference and procedures they’ve carefully written and edited are t
…
Help agents understand your site
Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.
Manage this listing → · Agent and API instructions
Machine-readable: GET /v1/resolve?q=passo.uno · GET /v1/domain/passo.uno · this page as Accept: application/json or text/markdown · MCP lookup_domain