Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →agentworkforce/github-oauth-nango-integration
Use when implementing GitHub OAuth + GitHub App authentication with Nango - provides two-connection pattern for user login and repo access with webhook handling
Passed 21 of 22 test cases with the skill, and 5 of 22 without it.
and 26 more in the full report
16 fixed5 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
What constant identifiers should we define in TypeScript to represent Nango integrations when setting up dual GitHub OAuth and GitHub App authentication?
| Checked | Without skill | With skill |
|---|---|---|
| Sets the user identity integration key identifier to github. | Missed | Passed |
| Uses separate integration keys to differentiate user authentication sessions from repository permission sessions. | Passed | Passed |
The instructions your model reads when the skill loads.
Implements dual-connection OAuth pattern: one for user identity (github integration), another for repository access (github-app-oauth integration). This separation enables secure login while maintaining granular repo permissions through GitHub App installations.
GitHub has two different authentication mechanisms that serve different purposes:
github integration)github-app-oauth integration)OAuth App alone: "User [email protected] logged in" → but which repos can they access?
GitHub App alone: "Installation #12345 has access to repo X" → but who is the user?
Solution: Two separate OAuth flows linked by user ID:
test cases passed, vs 5 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.