generated: '2026-08-08' method: generated source: openapi/britive-services-api-openapi.yml, openapi/britive-secrets-manager-api-openapi.yml, https://docs.britive.com/apidocs note: >- Britive publishes no AGENTS.md and no packaged Agent Skills of its own. These five are generated by API Evangelist and are grounded in real operationIds taken from Britive's published contract — every operationId named in every skill was checked against the specs in openapi/. Nothing here is invented. They mirror the platform's marquee flows and carry the cross-cutting rules an agent needs: the error-code contract, the absence of idempotency keys, the pagination shape, and the handling rules that a privileged-access product demands. skills: - name: britive-checkout-privileged-access file: britive-checkout-privileged-access.md api: Britive Services API summary: Just-in-time check-out of a privileged access profile, credential retrieval, and check-in. operations: [getMyAccess, myAccessUI, getAccessProfileSetting, checkoutProfile, profileApprovalRequest, getTokens, url, checkinProfile] - name: britive-terminate-active-sessions file: britive-terminate-active-sessions.md api: Britive Services API summary: Incident response — find and forcibly check in a user's active privileged sessions, then prove it in the audit log. operations: [getCheckedOutProfilesForAdmin_1, getCheckedOutProfilesForUser, checkInProfileForTransaction, checkInAllProfilesForUser, disabledStatuses, getAuditLogs] - name: britive-query-audit-logs file: britive-query-audit-logs.md api: Britive Services API summary: Query the audit log with a vocabulary-discovered filter expression, export CSV, and register an audit-log webhook. operations: [getFields, getOperators, getAuditLogs, getAuditLogsCsv, getAuditLogWebhooks, saveAuditLogWebhook, getAuditLogWebhookByNotificationMediumId, deleteAuditLogWebhookByNotificationMediumId] - name: britive-configure-shared-signals file: britive-configure-shared-signals.md api: Britive Services API summary: Register SSF issuers and receivers and map CAEP/RISC events to Britive actions, then verify in the results log. operations: [getSsfCatalog, listSsfIssuers, createSsfIssuer, getSsfIssuer, updateSsfIssuer, deleteSsfIssuer, getIssuerMappings, putIssuerMappings, listSsfReceivers, createSsfReceiver, getReceiverMappings, putReceiverMappings, querySsfResults] - name: britive-retrieve-secret file: britive-retrieve-secret.md api: Britive Secrets Manager API summary: Resolve the vault, walk the secret tree, and access a secret with justification and step-up authentication. operations: [getVaults, getVault, getOneLevelSecretData, getSecretMetaData, getSecretDataPost, getSecretData, downloadFile, listSecretVersions, getSecretDataForVersion, getApprovals] shared_rules: base_url: https://{tenant}.britive-app.com/api auth: 'Authorization: Bearer (single bearerAuth http/bearer scheme, applied globally)' error_envelope: '{status, message, errorCode, details} on application/json — see errors/britive-problem-types.yml' pagination: 'page (default 0), size (default 20), sort — no total count or next link is returned' idempotency: 'none published — a retry is a second request; see conventions/britive-conventions.yml' rate_limits: none published