Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

fetcher-cosec-auth

Étoiles15

Forks4

Mis à jour3 juin 2026 à 01:44

Use when implementing CoSec authentication with Fetcher, including CoSecConfigurer, JWT token lifecycle, token storage, refresh handling, device ID storage, multi-tenant space resolution, resource attribution, authorization headers, and 401 or 403 error handling.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Ahoo-Wang

Ahoo-Wang/fetcher

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	fetcher-cosec-auth
description	Use when implementing CoSec authentication with Fetcher, including CoSecConfigurer, JWT token lifecycle, token storage, refresh handling, device ID storage, multi-tenant space resolution, resource attribution, authorization headers, and 401 or 403 error handling.

fetcher-cosec-auth

Use This Skill When

The task mentions CoSec, JWT, bearer auth, token refresh, or authorization headers.
The task needs device ID tracking, tenant or space resolution, resource attribution, or policy-aware requests.
The task involves 401 retry, unauthorized redirects, or forbidden error handling.
The task needs CoSec interceptors attached to a Fetcher instance.

Workflow

Prefer CoSecConfigurer for app-level setup and use manual interceptors only for focused customization.
Decide token storage, device storage, token refresher, and space provider before attaching interceptors.
Register auth request/response interceptors only when refresh behavior is available.
Keep 401 retry and 403 handling separate so auth recovery does not hide authorization failures.
Load references/api.md for JWT classes, storage options, refresher contracts, headers, interceptors, and complete setup examples.

Key Practices

Treat tenant and owner attribution as request metadata, not hard-coded URL fragments.
Use cross-tab token storage behavior intentionally for multi-window apps.
Keep redirect/UI side effects in callbacks rather than inside low-level token classes.

References

references/api.md: Detailed package API, examples, and edge-case guidance. Load it only when the task needs CoSecConfigurer options, JWT token classes, TokenStorage, DeviceIdStorage, JwtTokenManager, TokenRefresher, CoSec headers, interceptors, space providers, and complete examples.

Related Skills

$fetcher-integration: Use for core Fetcher interceptor mechanics.
$fetcher-storage: Use for storage primitives behind token and device persistence.
$fetcher-react-hooks: Use for React security context and route guards.

Plus depuis ce dépôt

même dépôt

fetcher-decorator-service

Ahoo-Wang/fetcher

Use when creating declarative TypeScript API service classes with fetcher-decorator, including @api, HTTP method decorators, path/query/header/body/request parameters, result extractors, lifecycle hooks, inheritance, and reflect-metadata setup.

2026-05-2715

fetcher-eventbus

Ahoo-Wang/fetcher

Use when implementing typed event buses, serial or parallel event execution, BroadcastChannel or storage-based cross-tab messaging, handler priority, once handlers, name generation, or event synchronization across browser contexts.

2026-05-2715

fetcher-integration

Ahoo-Wang/fetcher

Use when setting up the core Fetcher HTTP client, NamedFetcher, fetcherRegistrar, HTTP methods, path and query parameters, interceptors, timeouts, result extractors, request lifecycle, status validation, or URL templates.

2026-05-2715

fetcher-llm-streaming

Ahoo-Wang/fetcher

Use when consuming Server-Sent Events, LLM token streams, OpenAI-style streaming chat responses, Fetcher eventstream helpers, response prototype extensions, stream termination detection, result extractors, or ReadableStream async iteration.

2026-05-2715

fetcher-openai-client

Ahoo-Wang/fetcher

Use when calling OpenAI Chat Completions through Fetcher, configuring OpenAI or ChatClient, sending streaming or non-streaming chat completion requests, adding interceptors, using completion result extractors, or handling OpenAI client errors.

2026-05-2715

fetcher-openapi-generator

Ahoo-Wang/fetcher

Use when generating type-safe Fetcher API clients from OpenAPI 3.x specs, including fetcher-generator CLI usage, CodeGenerator API, GeneratorConfiguration, parse and generation pipeline, model generation, client generation, barrel exports, and Wow CQRS generation support.

2026-05-2715

name	fetcher-cosec-auth
description	Use when implementing CoSec authentication with Fetcher, including CoSecConfigurer, JWT token lifecycle, token storage, refresh handling, device ID storage, multi-tenant space resolution, resource attribution, authorization headers, and 401 or 403 error handling.

fetcher-cosec-auth

Use This Skill When

The task mentions CoSec, JWT, bearer auth, token refresh, or authorization headers.
The task needs device ID tracking, tenant or space resolution, resource attribution, or policy-aware requests.
The task involves 401 retry, unauthorized redirects, or forbidden error handling.
The task needs CoSec interceptors attached to a Fetcher instance.

Workflow

Prefer CoSecConfigurer for app-level setup and use manual interceptors only for focused customization.
Decide token storage, device storage, token refresher, and space provider before attaching interceptors.
Register auth request/response interceptors only when refresh behavior is available.
Keep 401 retry and 403 handling separate so auth recovery does not hide authorization failures.
Load references/api.md for JWT classes, storage options, refresher contracts, headers, interceptors, and complete setup examples.

Key Practices

Treat tenant and owner attribution as request metadata, not hard-coded URL fragments.
Use cross-tab token storage behavior intentionally for multi-window apps.
Keep redirect/UI side effects in callbacks rather than inside low-level token classes.

References

references/api.md: Detailed package API, examples, and edge-case guidance. Load it only when the task needs CoSecConfigurer options, JWT token classes, TokenStorage, DeviceIdStorage, JwtTokenManager, TokenRefresher, CoSec headers, interceptors, space providers, and complete examples.

Related Skills

$fetcher-integration: Use for core Fetcher interceptor mechanics.
$fetcher-storage: Use for storage primitives behind token and device persistence.
$fetcher-react-hooks: Use for React security context and route guards.