{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github-lackeyjb--playwright-skill","slug":"lackeyjb--playwright-skill","name":"playwright-skill","type":"skill","url":"https://github.com/lackeyjb/playwright-skill","page_url":"https://unfragile.ai/lackeyjb--playwright-skill","categories":["automation"],"tags":["ai-tools","automation","browser-automation","claude","claude-code","claude-plugin","claude-skills","developer-tools","e2e-testing","model-invoked","nodejs","playwright","web-testing"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"github-lackeyjb--playwright-skill__cap_0","uri":"capability://code.generation.editing.model.invoked.browser.automation.code.generation","name":"model-invoked browser automation code generation","description":"Claude autonomously detects browser automation needs and generates custom Playwright code without explicit user commands, using a model-invoked pattern where the skill is registered as a claude-skill type in plugin metadata. The skill provides SKILL.md instructions (314 lines) that guide Claude's code generation patterns, enabling task-specific script creation rather than template-based execution. Claude reads progressive documentation and generates complete, executable Playwright automation scripts tailored to each specific testing or validation scenario.","intents":["I need Claude to automatically write and run browser tests without me specifying exact commands","I want Claude to detect when browser automation is needed and generate custom Playwright code for my use case","I need to automate form interactions, page testing, or validation workflows without pre-built templates"],"best_for":["developers building LLM-driven testing agents","teams wanting Claude to autonomously handle browser automation tasks","QA engineers who want AI-generated custom test scripts instead of template-based tools"],"limitations":["Claude must have sufficient context to understand the automation intent — vague requests may generate incorrect scripts","Model-invoked pattern depends on Claude's ability to recognize automation opportunities — not all use cases will trigger automatic invocation","Generated code quality depends on Claude's understanding of Playwright API and the specific testing scenario"],"requires":["Claude Code environment with plugin support","Node.js 16+ for Playwright execution","Playwright package installed (handled by skill setup)"],"input_types":["natural language description of automation task","URL or local application endpoint","test requirements or validation criteria"],"output_types":["executable JavaScript/Node.js code","test results and validation output","screenshots or visual artifacts"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_1","uri":"capability://automation.workflow.universal.module.resolution.with.path.normalization","name":"universal module resolution with path normalization","description":"The run.js executor handles dynamic path resolution using $SKILL_DIR environment variable substitution, ensuring Playwright and helper modules are correctly resolved regardless of installation location (plugin directory, standalone skill, or nested structure). The executor normalizes paths at runtime and manages module loading through Node.js require() with proper context isolation, eliminating module resolution errors that typically occur when skills are installed in different directory structures or nested plugin hierarchies.","intents":["I need browser automation to work whether the skill is installed as a plugin or standalone without path errors","I want to avoid 'module not found' errors when Claude-generated code tries to import Playwright or helpers","I need the skill to work in different installation contexts without requiring path configuration"],"best_for":["developers distributing Claude skills across different installation models","teams with nested plugin structures or monorepo setups","users installing skills in non-standard directory locations"],"limitations":["Path resolution adds ~50-100ms overhead per execution due to dynamic require() and environment variable substitution","Requires $SKILL_DIR environment variable to be set correctly by the Claude Code runtime","Symlinked or aliased installation paths may cause resolution issues if not properly configured"],"requires":["Node.js 16+ with require() module system support","Claude Code runtime that sets $SKILL_DIR environment variable","Playwright package available in node_modules (relative to resolved path)"],"input_types":["generated JavaScript code with require() statements","relative paths using $SKILL_DIR variable"],"output_types":["resolved module references","execution context with proper module scope"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_10","uri":"capability://automation.workflow.authentication.flow.automation.with.credential.handling","name":"authentication flow automation with credential handling","description":"Provides patterns and helpers for Claude-generated code to automate authentication flows including login forms, multi-factor authentication, OAuth flows, and session management. The skill documents authentication patterns in SKILL.md and provides helpers for common scenarios like filling login forms, handling redirects, and managing authentication state. Claude can generate code that handles complex authentication workflows without hardcoding credentials in scripts.","intents":["I want to automate testing of login flows and authentication without hardcoding credentials","I need to handle multi-factor authentication in automated tests","I want to test OAuth and third-party authentication flows"],"best_for":["teams testing authentication-protected applications","developers validating login flows and session management","QA engineers testing multi-factor authentication scenarios"],"limitations":["Hardcoding credentials in generated code is a security risk — requires environment variables or secure credential storage","MFA testing may require time-based codes (TOTP) or hardware tokens that are difficult to automate","OAuth flow testing requires mock providers or test accounts with third-party services","Session management and cookie handling can be fragile across different authentication systems"],"requires":["Environment variables or secure credential storage for test credentials","Knowledge of application's authentication mechanism","Optional: TOTP library for time-based MFA codes"],"input_types":["credentials (username, password, MFA codes)","authentication URLs and form selectors"],"output_types":["authenticated session/cookies","authentication success/failure results"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_11","uri":"capability://automation.workflow.network.interception.and.api.testing.with.request.response.inspection","name":"network interception and api testing with request/response inspection","description":"Enables Claude-generated code to intercept network requests and responses, mock API endpoints, and validate API behavior through Playwright's network interception capabilities. The skill provides patterns for inspecting request/response headers, mocking API responses, and testing error scenarios without relying on real backend services. Claude can generate code that validates frontend behavior against different API responses and error conditions.","intents":["I want to test how my application handles different API responses without a real backend","I need to mock API endpoints and validate frontend error handling","I want to inspect network requests to validate correct API calls are being made"],"best_for":["frontend developers testing API integration without backend dependencies","teams testing error handling and edge cases","developers validating correct API calls and request formats"],"limitations":["Network interception only works for requests made by the page — doesn't intercept requests from other processes","Complex API mocking scenarios may require external mock servers","Intercepting HTTPS requires certificate handling which can be complex","WebSocket and Server-Sent Events (SSE) interception is limited"],"requires":["Playwright network interception API support","Understanding of request/response structure for the APIs being tested"],"input_types":["request URL patterns","mock response data (JSON, status codes, headers)"],"output_types":["intercepted request/response data","mock response injection results","API validation results"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_12","uri":"capability://code.generation.editing.page.object.model.pattern.support.for.maintainable.test.code","name":"page object model pattern support for maintainable test code","description":"Provides documentation and patterns for Claude-generated code to implement the Page Object Model (POM) pattern, where page interactions are encapsulated in reusable page objects rather than scattered throughout test code. The skill documents POM patterns in SKILL.md, enabling Claude to generate well-structured, maintainable automation code that separates page structure from test logic. This pattern improves code reusability and makes tests more resilient to UI changes.","intents":["I want Claude to generate well-structured, maintainable automation code using Page Object Model","I need to encapsulate page interactions in reusable objects to reduce duplication","I want tests that are resilient to UI changes by centralizing selector management"],"best_for":["teams building large test suites with many pages/features","developers prioritizing test maintainability over quick automation","organizations with multiple developers working on the same test codebase"],"limitations":["POM adds abstraction overhead that may be unnecessary for simple tests","Requires discipline to maintain page objects as UI changes","Over-abstraction can make tests harder to understand for developers unfamiliar with POM","Claude may not always generate optimal page object structures"],"requires":["Understanding of Page Object Model pattern","Documentation in SKILL.md explaining POM patterns"],"input_types":["page structure and selectors","interaction patterns"],"output_types":["page object classes/modules","test code using page objects"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_13","uri":"capability://automation.workflow.ci.cd.integration.with.environment.aware.configuration","name":"ci/cd integration with environment-aware configuration","description":"Supports integration with CI/CD pipelines through environment variable configuration and headless mode support for server environments. The skill can detect CI/CD environment variables and adjust execution mode (headless vs visible), timeout settings, and retry behavior accordingly. Claude-generated code can be configured to run in CI/CD environments without modification by using environment-aware configuration patterns documented in SKILL.md.","intents":["I want to run the same automation scripts in both local development and CI/CD pipelines","I need the skill to automatically switch to headless mode in CI/CD environments","I want environment-specific configuration without modifying generated code"],"best_for":["teams integrating automation into CI/CD pipelines","developers wanting to run tests locally and in CI without code changes","organizations with complex CI/CD environments (Docker, Kubernetes, etc.)"],"limitations":["Headless mode in CI/CD may miss rendering issues visible in headed mode","CI/CD environments may have different browser capabilities or performance characteristics","Network access restrictions in CI/CD may prevent testing external services","Timeout and retry settings may need tuning for CI/CD performance"],"requires":["CI/CD environment variables (CI, GITHUB_ACTIONS, GITLAB_CI, etc.)","Headless browser support in CI/CD environment","Configuration patterns in SKILL.md for environment detection"],"input_types":["environment variables","configuration options"],"output_types":["environment-aware execution configuration","test results suitable for CI/CD reporting"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_2","uri":"capability://code.generation.editing.helper.function.library.with.reusable.automation.utilities","name":"helper function library with reusable automation utilities","description":"Provides a lib/helpers.js library of reusable utility functions that Claude-generated code can import and use, including common patterns for page navigation, element interaction, form filling, screenshot capture, and network interception. These helpers abstract away boilerplate Playwright code and provide consistent patterns for authentication flows, responsive testing, and visual validation, reducing the amount of code Claude needs to generate while improving consistency and reliability of generated automation scripts.","intents":["I want Claude to generate cleaner automation code by using pre-built helper functions instead of raw Playwright API calls","I need consistent patterns for common tasks like form filling, authentication, and screenshot capture across all generated tests","I want to reduce the complexity of generated code while maintaining full Playwright capabilities"],"best_for":["teams standardizing on automation patterns across multiple test scripts","developers who want Claude to generate more maintainable, readable code","organizations building custom helper libraries on top of Playwright"],"limitations":["Helper functions are opaque to Claude unless documented in SKILL.md — poorly documented helpers may not be used effectively","Adding new helpers requires updating both the library and SKILL.md documentation for Claude to discover them","Helper functions add an abstraction layer that may hide Playwright API details needed for advanced use cases"],"requires":["lib/helpers.js file present in skill directory","Node.js require() support for importing helpers","Playwright package available for helpers to wrap"],"input_types":["function calls from generated code","parameters matching helper function signatures"],"output_types":["Playwright browser/page objects","test results and validation data","screenshots or DOM state"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_3","uri":"capability://automation.workflow.automatic.development.server.detection.and.targeting","name":"automatic development server detection and targeting","description":"Implements automatic scanning of common development server ports (3000, 5173, 8080, etc.) to detect and target local applications without requiring explicit URL configuration. The skill detects running dev servers at startup and provides Claude with available targets, enabling automation against locally-running applications without users needing to specify ports or URLs. This pattern is documented in SKILL.md and integrated into the executor's initialization logic.","intents":["I want Claude to automatically find and test my local dev server without me specifying the port","I need the skill to detect which development server is running and target it automatically","I want to avoid hardcoding localhost:3000 or other port numbers in automation scripts"],"best_for":["developers with local development workflows using standard dev server ports","teams testing multiple applications with different port configurations","rapid prototyping scenarios where port numbers change frequently"],"limitations":["Only detects servers on common ports (3000, 5173, 8080, etc.) — custom ports require explicit configuration","Port scanning adds ~500ms-1s startup latency to detect available servers","May detect false positives if other services are running on common ports","Requires network access to localhost — doesn't work in restricted network environments"],"requires":["Development server running on one of the detected common ports","Network access to localhost","Node.js ability to make HTTP requests for port detection"],"input_types":["implicit (no user input required)","optional explicit port/URL override"],"output_types":["list of detected available servers","selected target URL for automation"],"categories":["automation-workflow","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_4","uri":"capability://automation.workflow.visible.browser.execution.with.real.time.observation","name":"visible browser execution with real-time observation","description":"Configures Playwright to run with headless: false by default, displaying the browser window during automation execution for real-time observation and debugging. This default configuration is set in SKILL.md instructions and allows developers to watch automation progress, see failures as they occur, and debug issues visually rather than relying solely on logs. The visible browser mode enables interactive debugging where developers can pause execution and inspect page state.","intents":["I want to see the browser window while automation is running to debug issues in real-time","I need to observe what Claude's generated automation is actually doing on the page","I want to pause and inspect page state during test execution for troubleshooting"],"best_for":["developers debugging automation scripts interactively","teams validating automation behavior visually before CI/CD deployment","QA engineers who need to understand test failures through visual inspection"],"limitations":["Visible browser mode requires a display/GUI environment — doesn't work in headless CI/CD environments without X11 forwarding","Adds ~200-500ms overhead per execution due to browser rendering and display management","Cannot be used in containerized environments without special display configuration","May cause timing issues if automation depends on specific rendering performance"],"requires":["Display server (X11 on Linux, native on macOS/Windows)","Playwright browser binaries with GUI support","Sufficient system resources for browser rendering"],"input_types":["implicit configuration (headless: false default)"],"output_types":["visible browser window","visual feedback during execution"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_5","uri":"capability://memory.knowledge.progressive.disclosure.documentation.with.on.demand.api.reference","name":"progressive disclosure documentation with on-demand api reference","description":"Implements a two-tier documentation system where SKILL.md (314 lines) provides concise instructions for Claude to understand basic automation patterns, while a comprehensive API reference (630 lines) is loaded on-demand when Claude needs detailed information. This progressive disclosure pattern reduces token usage and context overhead by providing only essential information upfront, with detailed API documentation available when Claude requests it. The documentation is structured to guide Claude's code generation while remaining accessible for human developers.","intents":["I want Claude to have enough documentation to generate automation code without overwhelming context size","I need detailed API reference available when Claude encounters complex automation scenarios","I want to keep the skill's context footprint small while maintaining comprehensive documentation"],"best_for":["Claude Code environments with token/context limitations","teams managing multiple skills where context efficiency matters","projects where documentation needs to be both AI-readable and human-readable"],"limitations":["Claude may not discover advanced API features if they're only in the on-demand reference","Two-tier documentation requires maintenance of both concise and detailed versions","On-demand loading adds latency when Claude needs to fetch detailed documentation","Documentation must be manually kept in sync between SKILL.md and API reference"],"requires":["SKILL.md file with concise instructions (314 lines)","Comprehensive API reference documentation (630 lines)","Claude Code environment that supports loading documentation on-demand"],"input_types":["implicit (documentation structure)"],"output_types":["concise instructions for Claude","detailed API reference when requested"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_6","uri":"capability://automation.workflow.artifact.based.code.execution.with.isolated.execution.context","name":"artifact-based code execution with isolated execution context","description":"Executes Claude-generated Playwright code as artifacts through the run.js executor, providing isolated execution context where generated code runs in a separate Node.js process with proper module scope and error handling. The executor captures stdout/stderr, handles execution errors gracefully, and returns results back to Claude, enabling a feedback loop where Claude can see execution results and iterate on generated code. This artifact execution pattern prevents generated code from interfering with the skill's own runtime.","intents":["I want Claude-generated code to run in isolation without affecting the skill's own runtime","I need to capture execution results and errors from generated automation scripts","I want Claude to see execution feedback and iterate on generated code based on results"],"best_for":["developers running untrusted or experimental generated code","teams needing execution isolation for security or stability","scenarios where generated code failures shouldn't crash the skill"],"limitations":["Isolated execution adds ~200-300ms overhead per code artifact due to process spawning","Inter-process communication (IPC) for results adds latency compared to in-process execution","Debugging generated code is more complex due to separate process context","Large output from generated code may hit IPC buffer limits"],"requires":["Node.js child_process module support","run.js executor script","Proper error handling and output capture mechanisms"],"input_types":["JavaScript/Node.js code as artifact","environment variables and configuration"],"output_types":["execution results (stdout/stderr)","error messages with stack traces","exit codes"],"categories":["automation-workflow","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_7","uri":"capability://tool.use.integration.plugin.distribution.with.nested.structure.support","name":"plugin distribution with nested structure support","description":"Distributes the skill as a Claude Code Plugin with metadata in .claude-plugin/plugin.json and .claude-plugin/marketplace.json, supporting both plugin installation (nested structure) and standalone skill installation. The plugin metadata registers the skill as a claude-skill type, enabling automatic discovery and invocation by Claude Code. The nested structure allows the skill to be distributed as a plugin while maintaining compatibility with standalone skill installations.","intents":["I want to distribute this skill through Claude Code's plugin marketplace","I need the skill to work both as a plugin and as a standalone installation","I want Claude to automatically discover and invoke this skill without manual registration"],"best_for":["skill developers publishing to Claude Code marketplace","teams distributing skills across multiple Claude Code installations","organizations wanting both plugin and standalone deployment options"],"limitations":["Plugin metadata must be maintained in sync with skill implementation","Nested plugin structure adds directory complexity compared to flat skill layout","Plugin marketplace distribution requires approval and may have publishing delays","Standalone and plugin installations may have different path resolution behavior"],"requires":["Claude Code environment with plugin support",".claude-plugin/plugin.json with proper metadata",".claude-plugin/marketplace.json for marketplace distribution"],"input_types":["plugin metadata (JSON)","skill implementation files"],"output_types":["installed plugin in Claude Code","registered skill available for invocation"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_8","uri":"capability://image.visual.visual.testing.and.screenshot.capture.with.comparison","name":"visual testing and screenshot capture with comparison","description":"Enables Claude-generated code to capture screenshots at various points in automation execution and perform visual testing through Playwright's screenshot API. The skill provides helpers and patterns for capturing full-page screenshots, element-specific screenshots, and visual regression testing by comparing screenshots across test runs. This capability allows validation of UI rendering, responsive design, and visual consistency without relying solely on DOM assertions.","intents":["I want to validate that the UI renders correctly at different points in the automation flow","I need to perform visual regression testing by comparing screenshots across test runs","I want to capture evidence of test execution for debugging and documentation"],"best_for":["QA teams performing visual regression testing","developers validating responsive design across breakpoints","teams needing visual evidence of test execution for documentation"],"limitations":["Screenshot comparison requires baseline images and diff tools — not built into the skill","Screenshots are sensitive to rendering differences (fonts, anti-aliasing) across environments","Large numbers of screenshots consume significant disk space","Cross-browser screenshot comparison requires running tests in multiple browsers"],"requires":["Playwright screenshot API support","Disk space for storing screenshot artifacts","Optional: image comparison library for visual regression (e.g., pixelmatch, resemble.js)"],"input_types":["page/element references from Playwright","screenshot options (fullPage, viewport, etc.)"],"output_types":["PNG/JPG screenshot files","visual comparison results"],"categories":["image-visual","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github-lackeyjb--playwright-skill__cap_9","uri":"capability://automation.workflow.mobile.and.responsive.design.testing.with.viewport.configuration","name":"mobile and responsive design testing with viewport configuration","description":"Enables Claude-generated code to test responsive design and mobile layouts by configuring Playwright's viewport settings and device emulation. The skill provides patterns for testing multiple viewport sizes, mobile device emulation (iPhone, Android), and responsive behavior validation. Claude can generate code that tests the same automation flow across different viewport configurations to validate responsive design without manual multi-device testing.","intents":["I want to test how my application behaves on mobile devices without physical devices","I need to validate responsive design across multiple viewport sizes","I want to test mobile-specific features like touch interactions and mobile viewport"],"best_for":["developers building responsive web applications","QA teams testing mobile compatibility without device labs","teams validating responsive design across breakpoints"],"limitations":["Device emulation doesn't replicate all mobile behaviors (network conditions, GPS, sensors)","Touch interaction emulation may not perfectly match real touch behavior","Mobile-specific bugs (browser quirks, rendering differences) may not be caught by emulation","Testing many viewport sizes multiplies execution time"],"requires":["Playwright device emulation support","Viewport configuration options in generated code"],"input_types":["viewport dimensions (width, height)","device names (iPhone, Android, etc.)","device configuration objects"],"output_types":["test results for each viewport/device","screenshots showing responsive behavior"],"categories":["automation-workflow","image-visual"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":37,"verified":false,"data_access_risk":"high","permissions":["Claude Code environment with plugin support","Node.js 16+ for Playwright execution","Playwright package installed (handled by skill setup)","Node.js 16+ with require() module system support","Claude Code runtime that sets $SKILL_DIR environment variable","Playwright package available in node_modules (relative to resolved path)","Environment variables or secure credential storage for test credentials","Knowledge of application's authentication mechanism","Optional: TOTP library for time-based MFA codes","Playwright network interception API support"],"failure_modes":["Claude must have sufficient context to understand the automation intent — vague requests may generate incorrect scripts","Model-invoked pattern depends on Claude's ability to recognize automation opportunities — not all use cases will trigger automatic invocation","Generated code quality depends on Claude's understanding of Playwright API and the specific testing scenario","Path resolution adds ~50-100ms overhead per execution due to dynamic require() and environment variable substitution","Requires $SKILL_DIR environment variable to be set correctly by the Claude Code runtime","Symlinked or aliased installation paths may cause resolution issues if not properly configured","Hardcoding credentials in generated code is a security risk — requires environment variables or secure credential storage","MFA testing may require time-based codes (TOTP) or hardware tokens that are difficult to automate","OAuth flow testing requires mock providers or test accounts with third-party services","Session management and cookie handling can be fragile across different authentication systems","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.27821523202279347,"quality":0.5,"ecosystem":0.6000000000000001,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.15,"quality":0.25,"ecosystem":0.1,"match_graph":0.45,"freshness":0.05}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:21.550Z","last_scraped_at":"2026-04-22T08:02:06.281Z","last_commit":"2025-12-19T16:23:38Z"},"community":{"stars":2473,"forks":166,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=lackeyjb--playwright-skill","compare_url":"https://unfragile.ai/compare?artifact=lackeyjb--playwright-skill"}},"signature":"pfjUhlGAVnea+VbwXZTsfeUNTi1C5hIMSOPq5pwsD/oJtxQ5VakFdcdTkGDOEYNkDHrCdBmgBP6LZKRpo1+qBA==","signedAt":"2026-06-21T22:14:20.755Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/lackeyjb--playwright-skill","artifact":"https://unfragile.ai/lackeyjb--playwright-skill","verify":"https://unfragile.ai/api/v1/verify?slug=lackeyjb--playwright-skill","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}