Information request handling

Log, clarify, and route statutory information requests within the legal response clock.

49|11|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill information-request-handling-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Information request handling
Source: https://github.com/vstorm-co/agenticos/tree/main/backend/app/core/catalog/skill_gallery/public-sector/foi-request-handling
Command: npx skills add https://github.com/vstorm-co/agenticos --skill information-request-handling-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Public-sector teams receive requests for recorded information across many inboxes and formats, and mishandling them — missing the statutory deadline, refusing improperly, or applying exemptions without authority — creates legal and reputational risk. This Skill ensures every request is recognised, logged, and routed correctly from day one. ## Core Features & Use Cases - Request Recognition: Identifies any written request for recorded information as statutory, even when it arrives as a complaint or social media message and never names the legislation. - Immediate Logging: Captures date received, requester and contact route, the verbatim ask, and whether it concerns personal data or general recorded information, since the regimes and clocks differ. - Narrow Clarification: Guides a single consolidated clarification message only when genuinely unclear, avoiding serial requests that read as obstruction. - Decision Routing: Assembles material and timeline for the information officer, who alone decides exemptions, redaction, cost limits, and public-interest tests. - Use Case: A citizen emails a council asking for all correspondence about a planning decision. The Skill logs the request verbatim, starts the statutory clock, and routes the assembled file to the information officer without the handler deciding anything. ## Quick Start Use this skill to log and route the attached information request that just arrived in our inbox.

Frequently Asked Questions about Information request handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle a freedom of information request that arrives by email?▼

Treat any written request for recorded information as statutory from the day it arrives, regardless of wording. Log the date received, requester contact route, and the verbatim request immediately, then route it to the information officer for any decision on exemptions or release.

Does a request need to mention FOI legislation to be valid?▼

No. A request counts even if it never names the legislation and arrives inside a complaint or a social media message. What matters is that it is a written request for recorded information.

When should I ask a requester to clarify their information request?▼

Only clarify when the request is genuinely unclear, and do it in one message listing every ambiguity. Serial clarification requests read as obstruction, and the statutory clock does not always stop while you wait.

Who decides exemptions and redactions on an information request?▼

The information officer decides exemptions, redaction, cost limits, and public-interest tests. The handler's role is to assemble the material and the timeline, not to refuse, apply exemptions, or release anything without review.

What is the difference between a personal data request and a general information request?▼

Requests for the requester's own personal data fall under a different regime with a different clock than requests for recorded information generally. Log which type it is at intake so the correct statutory timeline applies.