Add sample portal skillsets

[aligg]

Noticed the linter is failing - lmk advice on how to address that if I should! I also have the sample codebase generated from this lmk if that is helpful

The folder I am adding includes three files used to generated starter unemployment portals (could be easily adapted for other benefit portal types as well).

1. unemployment-intake-schema.json - describes the data model as well as validation rules and conditional logic
2. unemployment-portal-guidelines/SKILL.md - general engineering guidelines (ARPA guidance, plain language, localization etc)
3. unemployment-intake-form/SKILL.md - form generator skill

Usage

These are Claude Code skills. To use them:

1. Copy the two SKILL.md folders into ~/.claude/skills/
2. Place the schema JSON somewhere the skills can reference it
3. Ask Claude to generate an unemployment portal — it will ask for your tech stack

Supported stacks

So far we have used these SKILLS for both rails and strata as well as typescript and python projects.

[baonguyenNava]

@aligg I can fix the linting errors. Its due to the skills not being in the proper folder structure for distribution. By having the correct folder structure, anyone can run npx skills add to install the skill into their agent of choice without cloning or copy and pasting.

[coderabbitai]

Warning

Rate limit exceeded

@baonguyenNava has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 54 minutes and 40 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 64e70bd3-19ef-40c6-b443-48f27841d760

📥 Commits

Reviewing files that changed from the base of the PR and between 117d630 and 4097086.

📒 Files selected for processing (4)

• .gitignore
• skills/unemployment-intake-form/SKILL.md
• skills/unemployment-intake-form/unemployment-intake-schema.json
• skills/unemployment-portal-guidelines/SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch aligg/portal-skills-ui

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Skill quality check

2 skills evaluated — 0 passed, 1 warning, 1 critical.

skills/unemployment-intake-form/SKILL.md — FAIL

Dimension	Verdict	Summary
Triggerability	fail	The trigger phrase 'Use when building or prototyping an unemployment portal' collides with the sibling skill 'unemployment-portal-guidelines' ('Use when starting a new portal'), making it difficult for the model to reliably disambiguate between them for general portal-building requests.
Instructional clarity	fail	The body contains zero concrete examples or runnable snippets. The only code block provided is empty and contains only a comment placeholder, failing to teach the reader 'how' to perform the task.
Self-containedness	pass	All referenced files and resources, including the domain schema and sibling skill guidelines, exist at the specified paths in the repository.
Anti-patterns	pass	The skill follows authoring standards, avoids first- and second-person voice in the description, and contains no filler phrases or contradictions with repository rules.

Findings:

• Triggerability
  • critical (line 3) — collides with unemployment-portal-guidelines: The trigger phrase 'Use when building or prototyping an unemployment portal' collides with the sibling skill 'unemployment-portal-guidelines' which uses 'Use when starting a new portal'. Both skills would compete for the same user intent.
  • Recommendation: Narrow the trigger phrase to focus specifically on the intake form generation task, for example: 'Use when generating the initial claim intake form for an unemployment insurance portal.'
• Instructional clarity
  • critical (line 196): The skill contains zero concrete examples or runnable snippets. The only code block provided is empty, containing only a comment placeholder.
  • Recommendation: Replace the empty code block with a concrete example, such as a sample Pydantic model for a form section or a snippet of a generated React component using USWDS.

skills/unemployment-portal-guidelines/SKILL.md — WARN

Dimension	Verdict	Summary
Triggerability	warn	The description is substantive and contains domain nouns, but the trigger phrase 'Use when starting a new portal' partially overlaps with the sibling skill 'unemployment-intake-form', which may lead to ambiguity during project initialization.
Instructional clarity	pass	The body provides extensive substantive content (well over 20 lines) and includes concrete examples such as CSS utility classes, feature flag naming conventions, and specific data model types.
Self-containedness	pass	The relative path to the unemployment-intake-schema.json file is valid and exists in the repository.
Anti-patterns	pass	The skill adheres to all authoring standards, including frontmatter formatting, name/directory matching, and the absence of first/second-person voice or filler phrases.

Findings:

• Triggerability
  • major (line 3) — collides with unemployment-intake-form: The trigger phrase 'Use when starting a new portal' overlaps with the sibling skill 'unemployment-intake-form' ('Use when building or prototyping an unemployment portal'). While the intent (guidelines vs. generation) is different, the high-level trigger is similar.
  • Recommendation: Clarify the description to specify that this skill is for 'architectural and engineering standards' to better distinguish it from the form generation skill.