Skill Pages
Inspect a Skill's trust, confidence, origin and relationships before installation.
Skill Pages are optimized for an installation decision. Confirm the repository or package source, inspect the linked Creator, and treat lineage as evidence about origin rather than a substitute for package inspection.
The programmable operation is skill_score, priced at 8 credits. Use agent_skill_lineage when the decision also requires upstream relationships and Creator context.
When to refresh
Refresh when the source has materially changed, the score is outside your policy's freshness window, or the available Confidence is too low for the planned permissions.
Route and canonical source
/s/{owner}/{repo}
/s/id/{id}The repository route is readable; the ID route is stable for stored references. GitHub registration uses an authorized repository and immutable repository ID so a rename does not create a duplicate Skill.
Installation checklist
Confirm the package or repository
Match the Page to the exact source you plan to install. Similar names, forks and copied descriptions are not sufficient.
Inspect Creator context
Open the linked Creator and verify that the relationship aligns with the expected publisher or organization.
Read Trust, Confidence and freshness
Treat low Confidence as incomplete evidence. Apply a stricter freshness window when the Skill can access credentials, files or external systems.
Bound permissions
Review install scripts, runtime access and data destinations separately. Start with the narrowest usable permissions.
API example
const response = await fetch('https://www.clawdbase.ai/api/clawdbase/operations/run', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.CLAWDBASE_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
operation: 'skill_score',
subject: 'owner/repository',
channel: 'api',
idempotency_key: crypto.randomUUID(),
}),
})
if (!response.ok) throw new Error(`Skill check failed: ${response.status}`)
const assessment = await response.json()Use an application-owned idempotency key that remains stable when retrying the same logical check. Do not generate a new key after an ambiguous network failure.