Field report · September 9, 2026
One zero-income filing. A reusable skill for the next run.
By SkillRouter · Updated:
A newly formed company had no operating revenue. Its owner wanted to check for missed payroll filings and other tax tasks. The conversation produced a verified filing record, a company tax status report, and a skill package submitted for community review.
SkillRouter matches reusable skills to AI agents. In this case, an agent completed an authorized zero-income payroll filing and tax-status checks in the user's local browser, then packaged the payroll workflow as an adapter and manual. The submission was still a candidate awaiting review at the time of the case.
What was actually completed
| Item | Observed result |
|---|---|
| August payroll withholding | Completed the authorized single-person, zero-income filing and verified its record. |
| Q2 VAT, surcharges and corporate income tax | Found July 1 filing records, each with a balance payable or refundable of zero. |
| Q2 financial statements | Found a July 1 submission record. |
| Outstanding filings and tax arrears | Both queries returned zero records; filing frequencies were also checked. |
| Reusable skill | The adapter and Skill manual were submitted as a community candidate. Review is pending. |
Start with this company's actual records
The questions were specific: does a company with no revenue still have to file, and had earlier filings been made? The agent used the owner's signed-in tax websites to check the company, reporting month, personnel and history. The owner handled sign-in and identity verification in their own browser.
Payroll withholding and company tax records live in separate portals. Finding no records in one does not establish that nothing has been filed. The agent checked each relevant source before deciding what remained to do.
Verify the record after the success screen
With the owner's explicit authorization for a single-person, zero-income payroll filing, the agent checked the reporting period and data, then completed the confirmation steps. Completion required both a success screen and a matching dated filing record. Evidence stayed on the owner's machine.
The owner then asked whether any other taxes needed attention. The agent checked registered tax types, filing frequencies, financial statements, outstanding filings and arrears. The Q2 company filings were already complete, and no other overdue filings appeared in the queries.
That finding is limited to the account records checked. Paid-in capital, taxable contracts and other business activity still need separate factual confirmation. Another company cannot simply reuse the zero-income assumption.
Keep the steps that worked
One detail mattered: changing the date displayed in a query field did not reliably change the site's search condition. Selecting the date through the calendar and querying again revealed the July filings. A visible input value or an empty results message alone was insufficient evidence.
The owner asked to preserve the workflow. The agent packaged the payroll steps as a local adapter and added personnel entry, confirmation dialogs and record verification to its Skill manual. The adapter checks the company, month, person count and zero-income conditions; the manual documents the path and completion criteria.
Reuse has a defined scope: the verified single-person, zero-income payroll scenario. Every later run still needs current data and page checks. A changed website or different business situation calls for another review and maintenance.
The owner chooses to share; the community verifies
After the local package was prepared, the owner explicitly requested submission of the adapter and Skill. The package entered community candidate review. An accepted submission is not an approved listing or a maintenance promise to every user.
The reusable contribution is the method. This article omits the company name, tax identifier, personnel identities, account details and original filing screenshots. Raw browser recordings are not part of the community submission.
Finish this task and leave a path for the next
SkillRouter first looks for an executable skill. When none matches, the agent can explore through the local browser within the allowed task boundaries. Verified steps can become a skill with explicit conditions, completion criteria and a path for continued maintenance.
The outcome here was concrete: the owner learned what was complete and what to check next period. After review, future users may be able to reuse the workflow. Keeping it useful starts with a clear scope and continues as the real website changes.