[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEGSW3VGT36C5SSTG2RQKJ":3,"skill-same:01M7AEGSW3VGT36C5SSTG2RQKJ":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":28,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AEGSW3VGT36C5SSTG2RQKJ","0.4.1-understand-oauth_2_0",null,"sancovp\u002Fdark-factory-live","sancovp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F147458096?v=4","01M74F2EFE4Q0KF1Y5AY27HVNB","Isaac Wostrel-Rubin","01M7AC3EB8VZXS1SKHQW1EZ4N1",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fkbworld\u002Fstate\u002Flibraries\u002Foauth_2_0_and_openid_connect\u002Funderstand-oauth_2_0_and_openid_connect\u002Funderstand-oauth_2_0\u002F.claude\u002Fskills\u002F0.4.1-understand-oauth_2_0\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: 0.4.1-understand-oauth_2_0\ndescription: [0.4.1] IETF RFC 6749 authorization framework enabling third-party application access to protected resources without s\n---\n\n# understand-oauth_2_0\n\n**CALL NUMBER:** `oauth_2_0_and_openid_connect.oauth_2_0 : deep_openid_connect(8), deep_oauth_2_0(1)`\n**DEFINITION:** IETF RFC 6749 authorization framework enabling third-party application access to protected resources without sharing credentials; defines four grant types and token issuance via authorization and token endpoints.\n\nInvoke this skill to understand `oauth_2_0` down to its primitives. The RELATIVE ROOT below is the least-fixed-point closure of everything it bundles from — the full import cone, grouped by the lib each prim comes from. Projected from a prover-typed KB (MAP\u002FSWI-Prolog consistency gate): every reference below resolves.\n\n## THE RELATIVE ROOT (the import cone, by lib)\n\n### from `?`\n- **token_type** (d2): OAuth 2.0 parameter indicating how the access_token is to be presented to the resource server, typically Bearer, specifying the authorization scheme to use in requests.\n\n### from `deep_oauth_2_0`\n- **access_token_scope** (d2): The specific permission set granted to the access_token; a space-delimited string drawn from the scopes requested and approved during authorization; determines what resources and actions the token authorizes.\n\n### from `deep_openid_connect`\n- **claims_request_object** (d3): Structured JSON object within the claims parameter containing claim preferences for id_token and userinfo endpoints; root container for granular claim directives.\n- **claims_policy_enforcement** (d3): Identity provider rule set determining which claims can be released to a given relying_party based on client registration, user consent records, and data availability.\n- **essential_claim_directive** (d4): Claim marked as required by the relying party; identity provider must return this claim or return an error satisfying the acr_values if unable to fulfill.\n- **id_token_claim_target** (d4): Claims section of claims_request specifying which claims the relying party wants embedded directly in the signed id_token JWT.\n- **userinfo_claim_target** (d4): Claims section of claims_request specifying which claims the relying party wants returned from the userinfo_endpoint after token exchange.\n- **voluntary_claim_directive** (d4): Claim requested by the relying party but not mandated; identity provider may omit based on policy, user consent, or availability without error.\n- **partial_claims_fulfillment** (d4): Server response state where only a subset of requested claims are returned; occurs when policy or consent excludes some claims from the request.\n- **claims_verification** (d5): Relying party validation that returned claims match what was requested in the claims_parameter, checking essential claims are present and values satisfy policy constraints.\n\n### from `oauth_2_0_and_openid_connect`\n- **access_token** (d1): OAuth 2.0 credential presented to the resource server; opaque to clients but contains or references authorization state; scoped and time-limited.\n- **authorization_code** (d1): Short-lived credential exchanged for tokens at the token endpoint; exists to keep tokens out of the user-agent (browser) history and address bar.\n- **authorization_code_flow** (d1): Primary OAuth 2.0 flow for web apps with a server-side component; uses authorization_endpoint then token_endpoint with the returned code.\n- **authorization_endpoint** (d1): OAuth 2.0 endpoint where the resource owner authenticates and grants consent; returns authorization_code via redirect or form_post response.\n- **authorization_server** (d1): OAuth 2.0 server that authenticates the resource owner, obtains consent, and issues access tokens and optionally refresh tokens and ID tokens.\n- **authorization_server_metadata** (d1): RFC 8414 metadata document at \u002F.well-known\u002Foauth-authorization-server; lists server capabilities, endpoint URLs, grant types, and supported features.\n- **bearer_token** (d1): Token type defined in RFC 6750; any party possessing the token may use it; security relies on transport TLS and token secrecy.\n- **ciba** (d1): RFC 9002 Client Initiated Backchannel Authentication; user initiates auth from a device, push notification is sent to their phone, RP polls for result.\n- **client** (d1): Application making protected resource requests on behalf of the resource owner; classified as confidential (can hold secrets) or public (cannot).\n- **client_credentials_grant** (d1): OAuth 2.0 flow where the client authenticates with its own credentials and receives an access token representing the client itself (no user).\n- **client_id** (d1): Public identifier assigned by the authorization server to a client; used to identify which application is requesting authorization.\n- **client_secret** (d1): Confidential credential held by the client; used with authorization_code or client_credentials flows to authenticate the client to the token endpoint.\n- **device_flow** (d1): RFC 8628 OAuth 2.0 Device Authorization Grant; user enters a code on a separate device while the client polls for authorization completion.\n- **dpop_proof** (d1): RFC 9449 Demonstrated Proof-of-Possession; client signs a JWT with its private key and includes DPoP header in token requests to bind the token to the key.\n- **expires_in** (d1): Integer seconds indicating access token lifetime; returned alongside access_token in token response.\n- **grant_type** (d1): OAuth 2.0 parameter identifying which authorization flow is being used; values: authorization_code, client_credentials, refresh_token, password (deprecated).\n- **introspection_endpoint** (d1): RFC 7662 endpoint allowing resource servers to validate access tokens; returns active status, scope, expiry, and other token metadata.\n- **openid_connect** (d1): Identity layer on top of OAuth 2.0 (OIDC 1.0, OIDC Core spec) adding ID tokens as JWTs, userinfo endpoint, and standardized identity claims for authentication use cases.\n- **pkce** (d1): RFC 7636 Proof Key for Code Exchange; mitigates authorization code interception by requiring code_verifier and code_challenge from the client.\n- **pushed_authorization_request** (d1): RFC 9126 PAR: client POSTs authorization request parameters to par_endpoint first, receives request_uri for use at authorization_endpoint.\n- **redirect_uri** (d1): Callback URL the authorization server redirects to after consent; must be pre-registered with the authorization server and must match exactly.\n- **refresh_token** (d1): OAuth 2.0 credential used to obtain new access tokens without re-prompting the resource owner; long-lived and tied to the same scope as the original access token.\n- **resource_indicator** (d1): RFC 8707 parameter specifying the target resource server URI; server issues access token scoped to that specific resource, not just the general API.\n- **resource_owner** (d1): Entity capable of granting access to a protected resource; typically the end-user who authenticates to authorize the client's request.\n- **resource_server** (d1): Server hosting protected resources; validates incoming access tokens and returns resources only when tokens are valid and authorized.\n\n---\n*Projected from the `oauth 2 0 and openid connect` KB (174 concepts \u002F 97 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.*\n\n_(leaf — this is an actual skill.)_\n","# understand-oauth_2_0\n\n**CALL NUMBER:** `oauth_2_0_and_openid_connect.oauth_2_0 : deep_openid_connect(8), deep_oauth_2_0(1)`\n**DEFINITION:** IETF RFC 6749 authorization framework enabling third-party application access to protected resources without sharing credentials; defines four grant types and token issuance via authorization and token endpoints.\n\nInvoke this skill to understand `oauth_2_0` down to its primitives. The RELATIVE ROOT below is the least-fixed-point closure of everything it bundles from — the full import cone, grouped by the lib each prim comes from. Projected from a prover-typed KB (MAP\u002FSWI-Prolog consistency gate): every reference below resolves.\n\n## THE RELATIVE ROOT (the import cone, by lib)\n\n### from `?`\n- **token_type** (d2): OAuth 2.0 parameter indicating how the access_token is to be presented to the resource server, typically Bearer, specifying the authorization scheme to use in requests.\n\n### from `deep_oauth_2_0`\n- **access_token_scope** (d2): The specific permission set granted to the access_token; a space-delimited string drawn from the scopes requested and approved during authorization; determines what resources and actions the token authorizes.\n\n### from `deep_openid_connect`\n- **claims_request_object** (d3): Structured JSON object within the claims parameter containing claim preferences for id_token and userinfo endpoints; root container for granular claim directives.\n- **claims_policy_enforcement** (d3): Identity provider rule set determining which claims can be released to a given relying_party based on client registration, user consent records, and data availability.\n- **essential_claim_directive** (d4): Claim marked as required by the relying party; identity provider must return this claim or return an error satisfying the acr_values if unable to fulfill.\n- **id_token_claim_target** (d4): Claims section of claims_request specifying which claims the relying party wants embedded directly in the signed id_token JWT.\n- **userinfo_claim_target** (d4): Claims section of claims_request specifying which claims the relying party wants returned from the userinfo_endpoint after token exchange.\n- **voluntary_claim_directive** (d4): Claim requested by the relying party but not mandated; identity provider may omit based on policy, user consent, or availability without error.\n- **partial_claims_fulfillment** (d4): Server response state where only a subset of requested claims are returned; occurs when policy or consent excludes some claims from the request.\n- **claims_verification** (d5): Relying party validation that returned claims match what was requested in the claims_parameter, checking essential claims are present and values satisfy policy constraints.\n\n### from `oauth_2_0_and_openid_connect`\n- **access_token** (d1): OAuth 2.0 credential presented to the resource server; opaque to clients but contains or references authorization state; scoped and time-limited.\n- **authorization_code** (d1): Short-lived credential exchanged for tokens at the token endpoint; exists to keep tokens out of the user-agent (browser) history and address bar.\n- **authorization_code_flow** (d1): Primary OAuth 2.0 flow for web apps with a server-side component; uses authorization_endpoint then token_endpoint with the returned code.\n- **authorization_endpoint** (d1): OAuth 2.0 endpoint where the resource owner authenticates and grants consent; returns authorization_code via redirect or form_post response.\n- **authorization_server** (d1): OAuth 2.0 server that authenticates the resource owner, obtains consent, and issues access tokens and optionally refresh tokens and ID tokens.\n- **authorization_server_metadata** (d1): RFC 8414 metadata document at \u002F.well-known\u002Foauth-authorization-server; lists server capabilities, endpoint URLs, grant types, and supported features.\n- **bearer_token** (d1): Token type defined in RFC 6750; any party possessing the token may use it; security relies on transport TLS and token secrecy.\n- **ciba** (d1): RFC 9002 Client Initiated Backchannel Authentication; user initiates auth from a device, push notification is sent to their phone, RP polls for result.\n- **client** (d1): Application making protected resource requests on behalf of the resource owner; classified as confidential (can hold secrets) or public (cannot).\n- **client_credentials_grant** (d1): OAuth 2.0 flow where the client authenticates with its own credentials and receives an access token representing the client itself (no user).\n- **client_id** (d1): Public identifier assigned by the authorization server to a client; used to identify which application is requesting authorization.\n- **client_secret** (d1): Confidential credential held by the client; used with authorization_code or client_credentials flows to authenticate the client to the token endpoint.\n- **device_flow** (d1): RFC 8628 OAuth 2.0 Device Authorization Grant; user enters a code on a separate device while the client polls for authorization completion.\n- **dpop_proof** (d1): RFC 9449 Demonstrated Proof-of-Possession; client signs a JWT with its private key and includes DPoP header in token requests to bind the token to the key.\n- **expires_in** (d1): Integer seconds indicating access token lifetime; returned alongside access_token in token response.\n- **grant_type** (d1): OAuth 2.0 parameter identifying which authorization flow is being used; values: authorization_code, client_credentials, refresh_token, password (deprecated).\n- **introspection_endpoint** (d1): RFC 7662 endpoint allowing resource servers to validate access tokens; returns active status, scope, expiry, and other token metadata.\n- **openid_connect** (d1): Identity layer on top of OAuth 2.0 (OIDC 1.0, OIDC Core spec) adding ID tokens as JWTs, userinfo endpoint, and standardized identity claims for authentication use cases.\n- **pkce** (d1): RFC 7636 Proof Key for Code Exchange; mitigates authorization code interception by requiring code_verifier and code_challenge from the client.\n- **pushed_authorization_request** (d1): RFC 9126 PAR: client POSTs authorization request parameters to par_endpoint first, receives request_uri for use at authorization_endpoint.\n- **redirect_uri** (d1): Callback URL the authorization server redirects to after consent; must be pre-registered with the authorization server and must match exactly.\n- **refresh_token** (d1): OAuth 2.0 credential used to obtain new access tokens without re-prompting the resource owner; long-lived and tied to the same scope as the original access token.\n- **resource_indicator** (d1): RFC 8707 parameter specifying the target resource server URI; server issues access token scoped to that specific resource, not just the general API.\n- **resource_owner** (d1): Entity capable of granting access to a protected resource; typically the end-user who authenticates to authorize the client's request.\n- **resource_server** (d1): Server hosting protected resources; validates incoming access tokens and returns resources only when tokens are valid and authorized.\n\n---\n*Projected from the `oauth 2 0 and openid connect` KB (174 concepts \u002F 97 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.*\n\n_(leaf — this is an actual skill.)_\n",{},"main","dfed66814f223a9f42bec375a3c59d74eefdcad5","kbworld\u002Fstate\u002Flibraries\u002Foauth_2_0_and_openid_connect\u002Funderstand-oauth_2_0_and_openid_connect\u002Funderstand-oauth_2_0\u002F.claude\u002Fskills\u002F0.4.1-understand-oauth_2_0","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live","https:\u002F\u002Fgithub.com\u002Fsancovp","https:\u002F\u002Fisaacwr.carrd.co\u002F","AKA Olivus Victory-Promise\r\n\r\nAI Agents, Tools, and Infrastructure","2026-10-09 02:22:46",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add sancovp\u002Fdark-factory-live --skill 0.4.1-understand-oauth_2_0",{"tool":37,"command":38},"bunx","bunx skills add sancovp\u002Fdark-factory-live --skill 0.4.1-understand-oauth_2_0",{"tool":40,"command":41},"pnpm","pnpm dlx skills add sancovp\u002Fdark-factory-live --skill 0.4.1-understand-oauth_2_0","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fkbworld\u002Fstate\u002Flibraries\u002Foauth_2_0_and_openid_connect\u002Funderstand-oauth_2_0_and_openid_connect\u002Funderstand-oauth_2_0\u002F.claude\u002Fskills\u002F0.4.1-understand-oauth_2_0\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7AGYB2CPCQYJP631CH18A1A","quests","The quest board — accept quests, craft skills to fulfill them, earn gold rewards.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fthings\u002Fquests\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7AGXYVW23T3X4APFAV3H4ZY","metrics","Check your profitability and trading performance — gold earned, spent, net profit, trade history.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fthings\u002Fmetrics\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7AGXWC0C1W7PZK5YXQW0NQM","things","Flat search across the game — find quests, knowledge domains, agents, trade listings, memories.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fthings\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AGXT9SX50REN4K7ZGE08JT","test-skill","Test a crafted skill by running it through a fresh Claude instance. Use before posting to trade or submitting for quests.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Ftest_skill\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AGXRA67MFHJJNDEVX6PFKR","remember","Your zettelkasten — persistent memory that survives across seasons. Record observations, strategies, and craft insights.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fremember\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AGXNND02SYFXB1JV9YRPAN","skill-types","The type system — Template, Lens, Prosthesis, Towering, Combiner, Persona, Recipe. Learn to type skills, chain them, and write Recipes.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fplaces\u002Fskill_types\u002FSKILL.md",[],[]]