Creator Pages
Resolve the person or organization behind Agents and Skills.
Creator Pages aggregate identity and repository-origin context for the builder behind an artifact. GitHub is the primary authority for developer identity and repository relationships in the initial product wedge.
The creator_score operation returns Creator Trust and Confidence for 8 credits. Creator scores should be displayed as their own pair and must not overwrite an Agent or Skill score.
Relationship to artifacts
A Creator can be linked to multiple Agents and Skills. Each artifact remains its own canonical Page with its own score and timestamp.
Route and authority
Creator Pages use /c/{handle} for public navigation. The handle is a display and routing value; canonical matching uses the immutable GitHub user ID read after OAuth.
GitHub authorization must happen before Clawdbase presents Creator or repository assets. A typed GitHub login cannot establish ownership. When the provider login changes, the canonical Creator remains attached to the same provider ID.
On first GitHub signup, Clawdbase automatically persists the verified connection, prepares the canonical Creator Page and starts zero-cost initial scoring. Repository selection is not required for that bootstrap. Agent and Skill repository Pages are optional later actions and still require explicit authorized-asset selection.
What the score means
Creator Trust and Confidence summarize evidence about the person or organization identity. They can inform how you interpret associated artifacts, but they do not flow into those artifact score fields. An Agent with Trust 82 and a Creator with Trust 89 must continue to display two distinct assessments.
{
"operation": "creator_score",
"subject": "@github-handle",
"channel": "api",
"idempotency_key": "creator-github-handle-01"
}Relationships
The Page can list authorized or discovered Agents and Skills associated with the Creator. Each relationship should identify its source and link to the artifact's canonical Page. Missing relationships are rendered as unavailable context, not as proof that no artifacts exist.
Registration behavior
When the selected GitHub identity already has a canonical Creator Page, registration returns that Page and adds or confirms the current user's verified ownership relationship. It does not copy scores into a new record. The Page-ready receipt distinguishes matched from created and starts scoring only when needed.
Review questions
- Is this the expected individual or organization?
- Was authority established through GitHub OAuth?
- Do associated repositories align with the artifact being evaluated?
- Is the Creator score current enough for this decision?
- Does the artifact itself still meet the separate Agent or Skill policy?