CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

service-factory/gds-assessment-plugin

Granular 4-phase, 4-role GDS Service Standard assurance skills, panel orchestrator, and synthesis engine.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

team.mdskills/gds-assessment-how-to/examples/apply-for-a-blue-badge/alpha/team/

Team

Point 6. The discipline that owns the riskiest hypothesis has to be on the team. Name who would staff a beta without starting recruitment from nothing.

RoleCivil servant or supplierTime on this Alpha
Accountable civil servantHead of Customer Service, Northshire CouncilOne day a week
User researchCivil servantFull time
DesignCivil servantFour days a week
TechnologySupplier, two developersFull time, ended 6 November 2026
DeliveryCivil servant delivery managerThree days a week

Riskiest hypothesis, and the role that owns it: H3, that someone who cannot leave home can apply online. Owned by the user researcher.

Beta staffing, role by role: The same civil servants would stay. The supplier developers would not. A council developer is already in the web team and can join a beta without a new recruitment.

Funding line: Customer services improvement budget, confirmed for a private beta of up to four months. No date is set.

skills

gds-assessment-how-to

examples

apply-for-a-blue-badge

alpha

team

team.md

00-service-context.md

README.md

README.md

build_past_assessment_catalogue.py

create-evidence-kit.py

create-example.py

library_paths.py

reports_mcp_server.py

scrape_gds_reports.py

SKILL.md

.mcp.json

README.md

tile.json