Set up dependency and security hygiene from repository evidence, with a clear scope, source list, risk queue, and approval line.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this at the start of dependency or vulnerability work.
Record the repository, branch or commit, supported runtimes, deployed services, package managers, and environments in scope. Ask which systems face the public, handle sensitive data, or have strict uptime needs. List anything you cannot inspect.
Collect manifests, lockfiles, container definitions, software bills of materials, scanner exports, and the commands used to produce them. Date every external advisory and release note. Keep requested versions separate from installed versions.
Give the user:
You may inspect, rank, plan, and draft a patch or pull request. Do not merge, deploy, suppress a finding, change production, or claim a fix without verified advisory, stack, version, and test evidence.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.