Addy Osmani Agent Skills
An engineering workflow skill library covering API and interface design, browser testing, CI/CD, debugging, code review and git versioning. Aimed at software engineers who want an agent to follow an explicit senior-engineer procedure for common development tasks.
- Frontend development
- Testing
- CI/CD
Source: addyosmani/agent-skills · pinned commit 6ca0cd7
View source on GitHubLuluSkill lists this project so you can find it. A listing is not a security review or an endorsement, and nothing on this page is installed or run for you.
EDITORIAL GUIDE
Review API changes from the consumer’s point of view
The reviewed API-design entry emphasizes contracts and observable behavior. A clearer server implementation is useful only if callers can still interpret its responses.
LuluSkill’s own reading of this project, not a summary of its README. About 3 minutes to read
This guide is LuluSkill’s own judgement about when this project fits, written from the pinned version named above. It is not the author’s documentation, not a security review and not a recommendation. LuluSkill did not install, run or test the project to write it, and the guide is shown only while this listing still points at the commit it was written against.
When this project fits
This entry fits a proposed API or boundary change with known consumers. Its opening principles prioritize contracts, consistent errors and validation at the boundary. Use it to review what clients observe before selecting internal abstractions.
When to choose something else
Do not treat cleaner naming as sufficient compatibility evidence. Clients may depend on omitted fields, error shapes or response timing that an internal refactor overlooks. Nor does reading an API-design entry replace authentication, authorization or a threat-specific security review.
What to provide and what to expect
Supply existing request and response examples, consumer assumptions, failure cases and the intended extension. Expect a proposed contract with explicit validation and error behavior. Keep internal implementation details separate from behavior callers are entitled to rely on.
Tools, permissions and boundaries
A review needs the boundary code and representative consumers. Changing a shared contract requires coordination with its owners. External responses remain untrusted input; the entry does not make them valid merely because their source is familiar.
The tradeoff and an alternative
For a single endpoint, a small contract table and consumer test can be more effective than a broad architecture document. The entry is useful when teams repeatedly make inconsistent choices. Its cost is disciplined agreement and maintenance, not just writing more rules.
A small acceptance exercise
Proposed exercise: add an optional field while preserving an old client. Check absent versus empty values, a legitimate zero, malformed input and an upstream failure. Reject the change if the old client must guess a new error shape or receives data outside the agreed contract.
Source, version and what was actually read
The pinned API-design entry was read for its opening contract, validation, error and consumer-behavior principles. Other entries in the library and a working API implementation were not evaluated. LuluSkill did not install or run this project; the exercise above is a proposed reader check, not a reported result.
How to use this listing
LuluSkill publishes the description and the source link only. The skill itself stays in its author’s repository, and nothing here is installed, copied or run for you.
- Read what the skill helps with The summary above says which job the project is for. If that is not the job you have, this is probably not the listing you want.
- Open the original source and follow the author’s own instructions The link to the original project opens its author’s page. That page, not this one, is where the setup steps and any copying instructions live.
- Use it in a compatible AI assistant Skills of this kind are normally used inside an AI assistant that can read a folder of files on your computer. Which assistants support them is the author’s decision, so check their page before you start.
Who it is for
Somebody who already wants this one job done and is willing to follow the author’s setup steps. No programming knowledge is assumed, and this listing cannot tell you whether the project suits you.
Before you start
You need an AI assistant that supports skills, and you will be following somebody else’s instructions on your own computer. Read them before you run anything.
What you end up with
Whatever the author’s project produces. LuluSkill never runs it, so this page cannot promise a result, a file, or a level of quality.
Where it is normally used
Projects like this are usually used in an AI assistant that supports skills, such as an AI coding assistant. The author’s repository says which assistants it is written for; LuluSkill has not tested it with any of them.
Version checked
The source was checked at this commit: 6ca0cd7
Changes made to the repository after this commit have not been checked.
License
MIT, from the licence file in the source repository at the listed commit. Check the repository’s licence before you use or copy the project.
Listing only
LuluSkill lists this project only. It does not host, download or run its code.
What this page does not include
The project’s files and setup steps stay in its own repository. LuluSkill has not security-tested the project or confirmed which AI assistants it works with.
Report a problem or request removal
Rights holders and users can report licence, attribution, security or accuracy problems with this page. We respond within 48 hours and record every request in our review log.
Opens your email app. You can also write to contact@luluskill.com and include this page’s address.