Track the conditions, documents, and actions needed to complete a deal. Build a checklist from the purchase agreement, add findings from due diligence, and report progress, deadlines, and tasks that could delay completion.
Set up a corporate legal practice profile through guided questions about responsibilities, company context, document formats, and review thresholds. Select relevant practice areas, save their settings, and refresh individual modules or check connected services later.
Draft an internal investigation memo from the investigation log, or update an existing draft as new information arrives. The workflow flags outstanding priority sources and shows changes before revising the memo.
Turn due diligence findings, collected during a deal review, into briefings for executives, deal leads, or working teams. Highlight material issues, changes since the previous update, review progress, and decisions needed at the level each audience requires.
Review documents in a virtual data room for a business transaction, apply configured significance thresholds, and organize findings by category and severity. Produce a memo with document references, missing materials, and actions needed before closing.
Track filing deadlines and completion status for each legal entity and jurisdiction. Identify upcoming, overdue, and unknown items, review gaps in entity records, and export the tracker as CSV for sharing.
Track legal work after an acquisition closes, including counterparty consents, contract transfers, and purchase agreement deadlines. Build phased workplans from available deal documents, update progress, and produce status reports or CSV exports for review.
Organize legal work into separate client or matter folders. Create, list, switch, and archive matters while keeping their context separate, or detach the active matter to work with general practice settings.
Extract the same fields from a batch of contracts or other documents into a comparison spreadsheet. Each answer includes a source quote and location, while missing, ambiguous, and review-required information is clearly distinguished for human verification.
Verify Claude Agent SDK build and release scripts without network access. Run command-line workflows in an isolated environment with substitute commands to check version validation, installer handling, and retries without overwriting the developer’s installed Claude binary.
Review source code without running it to identify potential security vulnerabilities. Findings include severity, confidence, attack scenarios, and suggested fixes, delivered as JSON for further triage and Markdown for human review.
Check harness changes on a host without Docker by running the pinned Claude Code CLI against a local mock API server. Capture request headers and verify behavior using the authentication environment generated by the harness.
Turn raw security findings into a ranked list for engineering review. Check claims against source code, merge duplicates, assess how feasible exploitation is, and assign component owners, with results in JSON and Markdown.
Investigate an alert or suspicious identifier using logs and source code. Assess attack success, measure affected data and users, test the suspected flaw locally, and produce a response plan for human review and execution.
Hunt for signs of compromise in web and application logs without an initial alert. Establish normal activity, record investigative hypotheses, check source code, and reproduce issues locally before producing incident records and a report.
Adapt a C/C++ vulnerability pipeline to another language, target, or detection method. The workflow gathers requirements, proposes file changes for approval, updates the implementation, and validates it against a test target containing known bugs.
Build a threat model that identifies valuable assets, attack entry points, potential threats, and mitigation priorities. Use source code and past vulnerabilities, an interview with the application owner, or a combination of both.
Get started with vulnerability review through a guided practice target, from threat modeling to scanning and triage. Ask questions about the pipeline and receive answers grounded in its documentation and source, with references and a next command.
Turn security findings into candidate code fixes with review results and summaries. Depending on the input, use independent source review or a pipeline with execution checks, then provide diffs for a person to review and apply.
Generate TRES Finance reports as CSV or XLSX files, including transaction ledgers, balances, and cost basis reports. Verify that the export was actually created, monitor its completion, and return a download link.
Create an interactive HTML implementation plan that connects proposed behavior to mockups, code, and data structures. Readers can explore details, choose options, edit schemas, and return comments before development starts.
Extract unidentified external addresses from TRES Finance and export a deduplicated Excel workbook. An import-ready contacts sheet lets users add names and tags, while a reference sheet shows inferred networks, transaction counts, and USD volumes to help prioritize labeling.
Find the TRES Finance report that fits a task such as month-end close, audit preparation, or balance checks. Recommendations explain relevant Excel tabs and columns, useful filters, and the report identifier needed for API exports.
Check the TestDino connection and personal access token, then discover accessible organizations, projects, and available modules. Use the results to identify the correct projectId before starting project-specific work.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)