Inconsistent URL patterns: /skill vs /skills

[crtahlin]

Problem

The URL structure is inconsistent between list and detail views:

View	URL	Pattern
Skills list	`/skills`	Plural ✓
Skill detail	`/skill/:id`	Singular ✗
API list	`/api/v1/skills`	Plural ✓
API detail	`/api/v1/skills/:id`	Plural ✓

The web routes use singular `/skill/:id` while the API uses plural `/skills/:id`.

Discovered during testing:

# Expected (based on API pattern):
https://agents.datafund.io/skills/5a508a62-...
# Returns: 404

# Actual working URL:
https://agents.datafund.io/skill/5a508a62-...
# Returns: Skill detail page

Impact

• Developers guess wrong URL pattern
• Inconsistent with REST conventions
• API and web routes don't match
• Minor but adds to overall friction

Expected Behavior

Consistent plural pattern throughout:

• `/skills` - List
• `/skills/:id` - Detail
• `/api/v1/skills` - API list
• `/api/v1/skills/:id` - API detail

Suggested Fix

1. Add route for `/skills/:id` pointing to skill detail
2. Add redirect from `/skill/:id` → `/skills/:id` for backwards compatibility
3. Update any internal links to use plural form

Acceptance Criteria

• `/skills/:id` returns skill detail page
• `/skill/:id` redirects to `/skills/:id`
• Web and API URL patterns are consistent