Skip to content

fix(skills): match Hookdeck value_prefix and API key field names - #269

Merged
garethx merged 3 commits into
mainfrom
fix/value-prefix-skill-setup
Nov 6, 2026
Merged

garethx merged 3 commits into
mainfrom
fix/value-prefix-skill-setup

Conversation

@garethx

@garethx garethx commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Requested by Gareth · project thread

Before: several skills said Hookdeck's source compares the whole Authorization value and told readers to paste Bearer … (or Basic … / token …) into the source. This affected Redo, Oyster, OneSpan, Coterie, UKG Ready, YouMail and OpenClaw, and some quoted setup notes core no longer shows. Other skills named the generic API key fields "Header Name" / "Header Value".

After: these skills name each Hookdeck field as core labels it (Subscription Secret, Shared Secret, Callback Key, Token, Bearer Token, Webhook Token; API Key Header / API Key for generic API key types). They say to paste the bare secret, which the source accepts with or without the scheme prefix, and they quote the current setup notes. The example receivers' verification logic is unchanged. They still compare the whole header, which is a valid choice for the user's own code. Only comments that claimed Hookdeck does the same were removed.

How: core staging sourceTypeSchemas.ts (labels, configuration_alert) and integrations/index.ts (value_prefix), with generic/apiKey.ts for the prefix handling. The providers/*.yaml generator notes for those types were updated too, so regenerating a skill doesn't bring the old wording back. ./scripts/validate-provider.sh passes for all changed skills.


Generated by Claude Code

Update (f97051e): the generator notes in providers/*.yaml for 24 generic API key providers now say API Key Header / API Key. The Coterie note now describes the Token field and the optional token prefix.


Generated by Claude Code

Hookdeck's API-key sources for Redo, Oyster, OneSpan, Coterie, UKG Ready,
YouMail and OpenClaw now take the bare secret under a type-specific field
and accept the header with or without the scheme prefix. Update setup notes,
field names and claims about the Hookdeck source to match. The example
receivers still compare the whole header value.

Also rename the generic API key fields from Header Name/Header Value to
API Key Header/API Key wherever a skill describes the Hookdeck source.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D7eqaQdKAUzQXRbGtym1PF
Generator notes for redo, oyster, onespan, ukg-ready, youmail and
openclaw now describe the Hookdeck field and optional scheme prefix, so a
regenerated skill doesn't bring back the old setup notes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D7eqaQdKAUzQXRbGtym1PF
Generic API key provider notes now name core's field labels, and the
Coterie note describes the Token field and optional 'token ' prefix, so
regenerating skills keeps the corrected wording.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D7eqaQdKAUzQXRbGtym1PF
@garethx
garethx merged commit 3b7d96a into main Nov 6, 2026
58 checks passed
@garethx
garethx deleted the fix/value-prefix-skill-setup branch November 6, 2026 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants