Submit SISKA Activity

STT-NF students enter activities and achievements into SISKA through a multi-step form. The task combines category selection, bilingual names, dates, supporting files, and a final confirmation. A missed field or duplicate entry can create a record that needs manual correction.

Problem

Browser agents can fill forms, though a generic instruction gives them little protection against duplicates, wrong academic periods, or an early save. SISKA also requires an authenticated browser session and a supporting document that the user selects.

Role and scope

I documented the submission workflow as an installable agent skill. I wrote the main instructions, activity catalog, Chrome guide, batch workflow, and OpenAI interface metadata.

The skill does not store credentials or bypass login. It stops when the browser session, supporting file, date, or form state lacks required information.

Process and decisions

I placed a duplicate check before form entry and a user confirmation before the final save. After submission, the agent returns to the correct academic period and searches for the saved entry. The workflow ends only after the entry appears in the list.

The package separates stable instructions from reference material so an agent can load the detail needed for one path without mixing every activity category into the main workflow.

Packaged workflow

I published the complete skill with three reference guides, interface metadata, and installation instructions. Later revisions tightened the submission flow and made installation clearer.

I have not tracked installs, successful submissions, or error rates across users.

Limits

The workflow depends on the current SISKA interface and an authenticated Chrome session. UI changes can break selectors or category assumptions. The agent still needs the user to supply correct dates, supporting documents, and approval for the final save.