# Built in the open. Yours to improve. Every tool here is public, free, and open to pull requests. You do not need to write code to make a real difference to it: a corrected clause date or a note about how the work actually gets done is worth as much as a patch. ## Where the work lives Four repositories take contributions today. Each one has its own issues and its own README; start wherever your problem actually is. ### skills The Claude Code plugin marketplace and every skill in it, the FAR Clause Checker included. New skills, prompt fixes, and clause-data corrections all land here. ### GAO-Bid-Protest-Nexus The dashboard, the search backend, and the decision metadata behind the Nexus. A miscoded decision or a protest ground you would split differently is a useful issue. Code is Apache 2.0 and the data CC BY 4.0, over a corpus credited to Kevin Misener. ### mcps Model Context Protocol servers, the ones behind the coming-soon card on the homepage. Early enough that the shape of it is still open to argument. ### agents Agent definitions for acquisition work. Same story as the MCP servers: in progress, and the earlier the feedback the more it changes. ## What helps most In rough order of how rare it is, not how hard it is. A clause the checker passed that your reviewer caught, a deviation date that does not match the memo you are holding, a protest decision filed under the wrong ground. These are the highest-value reports on the project and the hardest to find without a practitioner looking. An issue with the clause number, the date you expected, and where you got it is enough; a citation to the memo makes it immediate. Most of what slows acquisition down is procedural, not technical, and it does not show up in any repository. How your office actually routes a Section I review, which step eats the afternoon, what you paste between two systems because nothing connects them. Workflow notes like these decide what gets built next as much as any feature request. Code, prompts, reference data, documentation, all welcome. Small and focused beats large and sweeping: one clause correction that is obviously right merges faster than a refactor that needs a conversation first. If a change is big enough that you would want agreement before writing it, open an issue and say what you have in mind. Install a skill, run the dashboard, and report what went wrong. Setup instructions that assume too much, an error that says nothing useful, a step that only works on one operating system. Nobody sees these except the person hitting them for the first time. ## Opening a pull request Nothing unusual. Fork, branch, change, push, open the request against the repository you started from. ``` git clone https://github.com/YOUR-USERNAME/skills.git cd skills git checkout -b fix-52-204-7-date # make the change git commit -am "Correct the 52.204-7 deviation date for HHS" git push -u origin fix-52-204-7-date ``` Then open the pull request from your fork on GitHub. Two things make a change easy to accept: say what you changed and why in the description, and for anything touching clause or decision data, cite the source you took it from. A deviation memo, a Smart Matrix entry, a GAO decision number. That way the correction can be verified without re-deriving it. Contributions carry the license of the repository they land in; each repository's README states which. ## Not on GitHub? Plenty of people with the most useful thing to say about a contracting tool do not have an account, and that should not be the end of it. ### Email it in Send the correction, the workflow note, or the bug report to acqagent.ai@gmail.com and it will be filed as an issue with credit, or kept off the record if you would rather it was. ### Browse the organization Every repository in one place, including the datasets and the earlier FAR and RFO experiments that are not linked from anywhere else on this site. If you work in federal acquisition, check your agency's rules on outside contribution and public statements before you post. Nothing here is worth a problem at work, and a note sent by email is always an option.