{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know","slug":"mcp-wesammustafa-claude-code-everything-you-need-to-know","name":"Claude-Code-Everything-You-Need-to-Know","type":"cli","url":"https://github.com/wesammustafa/Claude-Code-Everything-You-Need-to-Know","page_url":"https://unfragile.ai/mcp-wesammustafa-claude-code-everything-you-need-to-know","categories":["prompt-engineering"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_0","uri":"capability://automation.workflow.custom.slash.command.skill.system.with.markdown.based.workflow.automation","name":"custom slash command skill system with markdown-based workflow automation","description":"Enables developers to define reusable AI-assisted workflows as markdown files stored in .claude/commands/ directory. Each skill file contains prompts, instructions, and context that Claude executes when invoked via /skillname syntax. The system parses markdown metadata to extract skill definitions and automatically registers them as CLI commands, allowing non-programmers to extend Claude Code's capabilities without writing code.","intents":["I want to create a reusable workflow that Claude runs every time I type a specific command","I need to automate repetitive development tasks like code review or documentation generation","I want to share custom workflows with my team without requiring code changes"],"best_for":["teams building domain-specific development workflows","developers automating repetitive code generation patterns","non-technical team members creating AI-assisted processes"],"limitations":["Markdown-based skill definitions lack conditional logic or branching — all skills execute linearly","No built-in skill versioning or rollback mechanism","Skills cannot directly access external APIs without MCP server integration","Skill discovery is file-system based; no centralized registry or marketplace"],"requires":["Claude Code CLI installed and authenticated","Write access to .claude/commands/ directory","Understanding of markdown syntax and Claude prompt engineering"],"input_types":["markdown files with YAML frontmatter","user text input via CLI","project context from CLAUDE.md"],"output_types":["text responses","code snippets","structured markdown output"],"categories":["automation-workflow","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_1","uri":"capability://memory.knowledge.project.memory.persistence.via.claude.md.with.automatic.context.injection","name":"project memory persistence via claude.md with automatic context injection","description":"Maintains a CLAUDE.md file in the project root that stores persistent context, decisions, architecture notes, and project state. This file is automatically parsed and injected into every Claude interaction, eliminating the need to re-explain project context. The system treats CLAUDE.md as a living document that Claude can read and suggest updates to, creating a feedback loop where project knowledge accumulates across sessions.","intents":["I want Claude to remember my project architecture and decisions across multiple sessions","I need to maintain a single source of truth for project context that all team members see","I want Claude to suggest updates to project documentation based on code changes"],"best_for":["teams working on long-running projects requiring consistent context","solo developers who switch between projects frequently","projects with complex architecture that needs documentation"],"limitations":["CLAUDE.md is manually maintained — no automatic sync with code changes","Large CLAUDE.md files consume token budget; no built-in compression or summarization","No conflict resolution for concurrent edits to CLAUDE.md across team members","Context injection happens at prompt time, adding latency for very large files"],"requires":["CLAUDE.md file initialized via /init command in project root","Write permissions to project directory","Team agreement on CLAUDE.md update frequency and format"],"input_types":["markdown text","project architecture diagrams","decision logs"],"output_types":["markdown updates","context-aware code generation","architecture-aligned suggestions"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_10","uri":"capability://memory.knowledge.session.management.with.context.preservation.across.cli.invocations","name":"session management with context preservation across cli invocations","description":"Maintains session state across multiple CLI invocations, preserving conversation history, variable bindings, and execution context. Developers can continue conversations across separate claude commands without re-explaining context. Sessions are stored locally and can be resumed, forked, or archived, enabling complex multi-step workflows to be broken into manageable CLI invocations while maintaining continuity.","intents":["I want to continue a conversation with Claude across multiple CLI commands","I need to preserve context and variables between separate invocations","I want to fork a session to explore alternative approaches without losing the original"],"best_for":["developers working on complex tasks requiring multiple steps","teams collaborating on shared sessions","exploratory development where multiple approaches need to be tested"],"limitations":["Sessions are stored locally; no built-in synchronization across machines","Session size grows with conversation history; no automatic pruning or summarization","No access control for sessions; anyone with file access can read session history","Session forking creates duplicate context; no efficient branching mechanism"],"requires":["Local storage for session files (~/.claude/sessions/)","Sufficient disk space for conversation history","Session ID or name to resume/fork sessions"],"input_types":["CLI commands with session flags","conversation history"],"output_types":["session state","conversation history","variable bindings"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_11","uri":"capability://automation.workflow.built.in.command.interface.for.core.operations.and.system.control","name":"built-in command interface for core operations and system control","description":"Provides slash commands (/init, /model, /fast, /help, etc.) for core operations like project initialization, model selection, fast mode toggling, and help. Commands are implemented as built-in handlers in the CLI process and execute immediately without invoking Claude. The command interface is extensible; custom skills can be invoked as commands, creating a unified command namespace for both system operations and user-defined workflows.","intents":["I want to initialize a new project with Claude Code in one command","I need to switch models or toggle fast mode without editing configuration files","I want a consistent command interface for both system operations and custom workflows"],"best_for":["developers preferring CLI-based workflows over configuration files","teams standardizing on slash command conventions","projects with many custom commands requiring a unified interface"],"limitations":["Built-in commands are hardcoded; no dynamic command registration","Command help is static; no context-aware help based on project state","No command aliasing or abbreviation support","Command parsing is simple; no support for complex argument parsing or flags"],"requires":["Claude Code CLI installed","Understanding of available commands and their syntax"],"input_types":["CLI command strings"],"output_types":["command execution results","status messages","help text"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_12","uri":"capability://planning.reasoning.subagents.and.task.decomposition.for.hierarchical.problem.solving","name":"subagents and task decomposition for hierarchical problem solving","description":"Enables agents to spawn subagents to handle subtasks, creating hierarchical task decomposition. Parent agents can define subtasks, delegate to subagents, and aggregate results. Subagents inherit parent context (CLAUDE.md, project memory) but can have specialized prompts and tool bindings. This pattern enables complex problems to be solved through recursive decomposition without requiring manual task management.","intents":["I want to break down a large feature into subtasks and have agents work on them independently","I need agents to delegate work to specialized subagents without manual coordination","I want hierarchical task execution with automatic result aggregation"],"best_for":["teams solving complex problems that naturally decompose into subtasks","projects with clear hierarchical task structures","developers wanting to automate task delegation and coordination"],"limitations":["Subagent spawning adds latency; no built-in optimization for task scheduling","Context inheritance can lead to token bloat if parent context is large","No built-in deadlock detection if subagents have circular dependencies","Result aggregation is manual; no automatic merging of conflicting results"],"requires":["Agent orchestration framework with subagent support","Clear task decomposition strategy","Sufficient token budget for multiple agent executions"],"input_types":["parent task descriptions","subtask definitions"],"output_types":["subagent results","aggregated output","execution logs"],"categories":["planning-reasoning","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_13","uri":"capability://planning.reasoning.agent.teams.with.experimental.multi.agent.collaboration.patterns","name":"agent teams with experimental multi-agent collaboration patterns","description":"Provides experimental support for agent teams that collaborate on shared tasks using communication patterns like voting, consensus-building, and debate. Multiple agents with different perspectives or specializations work together to solve a problem, with a coordinator agent aggregating results and resolving disagreements. This enables more robust solutions by leveraging diverse viewpoints and reducing single-agent errors.","intents":["I want multiple agents with different expertise to review code and reach consensus","I need to explore multiple solution approaches and have agents debate tradeoffs","I want to reduce errors by having agents verify each other's work"],"best_for":["teams making critical decisions requiring multiple perspectives","projects where code review or architectural decisions benefit from diverse viewpoints","exploratory development where multiple approaches should be evaluated"],"limitations":["Agent teams are experimental; behavior and API may change","Multi-agent communication adds significant latency and token consumption","No built-in mechanism to break ties if agents disagree","Coordinator agent must manually aggregate results; no automatic consensus algorithm"],"requires":["Claude Code with experimental agent team support enabled","Multiple agent definitions with different specializations","Sufficient token budget for multi-agent execution"],"input_types":["shared task descriptions","agent specializations"],"output_types":["individual agent outputs","consensus results","debate transcripts"],"categories":["planning-reasoning","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_2","uri":"capability://planning.reasoning.multi.agent.orchestration.with.git.worktrees.for.parallel.development","name":"multi-agent orchestration with git worktrees for parallel development","description":"Enables spawning multiple AI agents that work in parallel on different branches using git worktrees. Each agent operates in an isolated working directory, executes tasks independently, and reports results back to a coordinator. The system manages branch creation, agent lifecycle, and result aggregation, allowing complex development tasks to be decomposed and executed concurrently by specialized agents (e.g., frontend, backend, database agents).","intents":["I want to parallelize development work across multiple features without manual branch management","I need specialized agents (frontend, backend, security) to work on the same codebase simultaneously","I want to decompose a large feature into subtasks and have agents work independently"],"best_for":["teams building large features that can be decomposed into parallel subtasks","projects with clear separation of concerns (frontend/backend/database)","developers wanting to explore multiple implementation approaches simultaneously"],"limitations":["Git worktrees require local disk space for each parallel branch — scales poorly beyond 5-10 agents","No built-in conflict resolution when agents modify overlapping code regions","Agent coordination happens via simple result aggregation; no sophisticated merge strategies","Requires manual intervention if agents encounter merge conflicts or dependency issues"],"requires":["Git repository with clean working directory","Git 2.15+ for worktree support","Sufficient disk space for multiple worktrees","Clear task decomposition strategy before spawning agents"],"input_types":["task descriptions","feature requirements","codebase state"],"output_types":["code changes in isolated branches","agent execution logs","merge-ready pull requests"],"categories":["planning-reasoning","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_3","uri":"capability://planning.reasoning.specialized.agent.templates.for.development.pipeline.roles","name":"specialized agent templates for development pipeline roles","description":"Provides pre-configured agent templates (Business Analyst, Project Manager, UX Engineer, Database Engineer, Frontend Engineer, Backend Engineer, Code Reviewer, Security Reviewer) that encapsulate role-specific prompts, tools, and decision-making patterns. Each template is instantiated as an agent with specialized context and MCP server bindings, enabling developers to delegate work to agents that understand domain-specific concerns and can operate autonomously within their expertise area.","intents":["I want a code review agent that understands our architecture and can review PRs autonomously","I need a security-focused agent to audit code for vulnerabilities before deployment","I want a database engineer agent to optimize queries and schema design"],"best_for":["teams with clear role separation and domain expertise","projects requiring specialized review or analysis (security, performance, UX)","organizations wanting to automate specific development pipeline stages"],"limitations":["Agent templates are static; customization requires modifying prompt files","No built-in feedback loop for agents to improve their own prompts based on outcomes","Agents operate independently without cross-role awareness or consultation","Template quality depends on manual prompt engineering; no automated optimization"],"requires":["Claude Code CLI with agent orchestration support","MCP servers configured for agent-specific tools (e.g., security scanner for Security Reviewer)","Project context in CLAUDE.md describing architecture and standards"],"input_types":["code files","pull requests","architecture documentation","security policies"],"output_types":["review comments","vulnerability reports","optimization suggestions","architectural analysis"],"categories":["planning-reasoning","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_4","uri":"capability://automation.workflow.model.selection.and.fast.mode.with.token.optimization","name":"model selection and fast mode with token optimization","description":"Provides /model command to switch between Claude Opus 4.6 (most capable), Sonnet 4.5 (balanced), and Haiku 4.5 (fastest/cheapest) models, and /fast toggle to enable fast mode which uses Haiku for initial reasoning then escalates to selected model if needed. The system tracks token usage across sessions and provides recommendations for model selection based on task complexity and budget constraints, enabling developers to optimize cost-performance tradeoffs.","intents":["I want to use the fastest model for simple tasks and the most capable model for complex reasoning","I need to control API costs by using cheaper models when possible","I want Claude to automatically choose the right model based on task complexity"],"best_for":["cost-conscious teams running many Claude interactions","developers prototyping with budget constraints","projects with variable task complexity requiring adaptive model selection"],"limitations":["Fast mode adds latency due to model switching overhead","No automatic fallback if Haiku fails to solve a problem in fast mode","Token tracking is session-based; no cross-session analytics or budgeting","Model selection is manual; no ML-based recommendation system"],"requires":["Anthropic API key with access to multiple Claude models","Claude Code CLI 1.0+","Understanding of model capabilities and cost differences"],"input_types":["CLI commands (/model, /fast)","task descriptions"],"output_types":["model selection confirmation","token usage statistics","cost estimates"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_5","uri":"capability://tool.use.integration.model.context.protocol.mcp.server.integration.with.semantic.code.intelligence","name":"model context protocol (mcp) server integration with semantic code intelligence","description":"Integrates MCP servers as external capability extensions configured in ~/.claude.json. Includes built-in Serena semantic code intelligence server that provides AST-based code analysis, symbol resolution, and codebase-aware context. Developers can register custom MCP servers for domain-specific tools (e.g., database clients, API integrations, security scanners), and Claude automatically discovers and uses available tools based on task context.","intents":["I want Claude to understand my codebase structure and symbol relationships without re-explaining them","I need to connect Claude to external tools like databases, APIs, or security scanners","I want to extend Claude Code with custom capabilities specific to my tech stack"],"best_for":["teams with complex codebases requiring semantic understanding","projects integrating with external systems (databases, APIs, CI/CD)","organizations building custom MCP servers for proprietary tools"],"limitations":["MCP server discovery is static (configured in ~/.claude.json); no dynamic registration","Tool selection is Claude's responsibility; no explicit control over which tools are used","MCP server latency adds to overall interaction time; no caching of tool results","Requires MCP server implementation knowledge to create custom servers"],"requires":["MCP server binaries or Node.js/Python runtimes for server implementations","~/.claude.json configuration with mcpServers array","API credentials for external services (if connecting to databases/APIs)"],"input_types":["code files","codebase queries","tool invocation requests"],"output_types":["semantic code analysis","symbol resolution results","external tool responses"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_6","uri":"capability://planning.reasoning.sequential.thinking.with.problem.decomposition.and.reasoning.chains","name":"sequential thinking with problem decomposition and reasoning chains","description":"Enables Claude to break down complex problems into sequential reasoning steps using extended thinking patterns. Developers can invoke sequential thinking mode to have Claude explicitly decompose tasks, explore multiple solution paths, and explain its reasoning before providing final answers. This is particularly useful for architectural decisions, debugging complex issues, and algorithm design where transparency and correctness are critical.","intents":["I want Claude to show its reasoning process for complex architectural decisions","I need to understand why Claude chose a particular implementation approach","I want Claude to explore multiple solutions before committing to one"],"best_for":["developers designing complex systems or algorithms","teams making architectural decisions requiring transparency","debugging scenarios where understanding the reasoning is as important as the solution"],"limitations":["Sequential thinking increases token consumption by 2-5x compared to direct responses","Reasoning chains cannot be easily edited or interrupted mid-execution","Extended thinking output is verbose; no built-in summarization of reasoning steps","Not suitable for time-sensitive tasks due to increased latency"],"requires":["Claude Opus 4.6 or Sonnet 4.5 (Haiku does not support extended thinking)","Sufficient token budget for 2-5x token consumption","Patience for longer response times"],"input_types":["complex problem descriptions","architectural questions","debugging scenarios"],"output_types":["reasoning chains","step-by-step decomposition","final recommendations with justification"],"categories":["planning-reasoning","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_7","uri":"capability://automation.workflow.hooks.system.for.automated.workflow.triggers.and.lifecycle.management","name":"hooks system for automated workflow triggers and lifecycle management","description":"Provides a hooks system that triggers custom skills or agents at specific lifecycle points (e.g., pre-commit, post-merge, on-file-change). Hooks are defined in CLAUDE.md or .claude/hooks/ and execute automatically when conditions are met, enabling developers to automate code quality checks, documentation updates, or deployment steps without manual invocation. The system integrates with git hooks and file watchers to detect trigger conditions.","intents":["I want to automatically run code review when a PR is created","I need to update documentation whenever code changes","I want to enforce code quality standards before commits"],"best_for":["teams enforcing consistent code quality standards","projects with complex deployment pipelines","developers wanting to automate repetitive pre-commit checks"],"limitations":["Hooks are synchronous; long-running hooks block git operations","No built-in error handling or rollback if hooks fail","Hook conditions are simple (file patterns, git events); no complex conditional logic","Debugging failed hooks requires manual log inspection"],"requires":["Git hooks support (pre-commit, post-merge, etc.)","File watcher capability (inotify on Linux, FSEvents on macOS)","Hook definitions in CLAUDE.md or .claude/hooks/"],"input_types":["git events","file change notifications","hook trigger conditions"],"output_types":["hook execution logs","automated code changes","quality reports"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_8","uri":"capability://tool.use.integration.playwright.based.browser.automation.for.web.testing.and.interaction","name":"playwright-based browser automation for web testing and interaction","description":"Integrates Playwright as an MCP server to enable Claude to automate browser interactions, perform web testing, and extract data from web applications. Claude can write and execute Playwright scripts to navigate pages, fill forms, take screenshots, and validate UI behavior. This enables end-to-end testing, web scraping, and UI validation workflows to be automated and integrated into development pipelines.","intents":["I want Claude to write and execute end-to-end tests for my web application","I need to automate web scraping or data extraction tasks","I want to validate UI behavior across different browsers and screen sizes"],"best_for":["teams building web applications requiring E2E testing","projects needing web scraping or data extraction","developers validating UI behavior without manual testing"],"limitations":["Playwright scripts are synchronous; no built-in support for async operations or timeouts","Browser automation is slow compared to unit tests; not suitable for rapid iteration","Screenshots and visual validation require manual inspection; no built-in image comparison","Requires browser binaries (Chromium, Firefox, WebKit) adding ~500MB disk space"],"requires":["Playwright MCP server installed and configured","Browser binaries (installed via playwright install)","Target web application running and accessible","Network connectivity to target URLs"],"input_types":["web URLs","test scenarios","form data"],"output_types":["Playwright scripts","test results","screenshots","extracted data"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-wesammustafa-claude-code-everything-you-need-to-know__cap_9","uri":"capability://automation.workflow.configuration.management.with.claude.json.for.global.settings.and.mcp.server.registration","name":"configuration management with ~/.claude.json for global settings and mcp server registration","description":"Centralizes all Claude Code configuration in ~/.claude.json, including API keys, model preferences, MCP server definitions, and user settings. The configuration file uses JSON schema with support for environment variable interpolation, enabling developers to manage settings across machines and share configurations with teams (minus sensitive credentials). Changes to ~/.claude.json are applied immediately without restarting the CLI.","intents":["I want to configure Claude Code once and have settings apply across all projects","I need to register multiple MCP servers and switch between them easily","I want to share team configuration without exposing API keys"],"best_for":["teams standardizing Claude Code configuration across developers","developers managing multiple MCP servers and model preferences","organizations with centralized API key management"],"limitations":["No built-in validation of ~/.claude.json; invalid JSON silently fails","Environment variable interpolation is basic; no complex templating","No version control for configuration changes; no rollback mechanism","Sensitive credentials stored in plaintext; requires OS-level file permissions"],"requires":["Write access to ~/.claude.json","Understanding of JSON syntax","API keys for Anthropic and any external services"],"input_types":["JSON configuration","environment variables"],"output_types":["applied settings","MCP server registrations"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":45,"verified":false,"data_access_risk":"high","permissions":["Claude Code CLI installed and authenticated","Write access to .claude/commands/ directory","Understanding of markdown syntax and Claude prompt engineering","CLAUDE.md file initialized via /init command in project root","Write permissions to project directory","Team agreement on CLAUDE.md update frequency and format","Local storage for session files (~/.claude/sessions/)","Sufficient disk space for conversation history","Session ID or name to resume/fork sessions","Claude Code CLI installed"],"failure_modes":["Markdown-based skill definitions lack conditional logic or branching — all skills execute linearly","No built-in skill versioning or rollback mechanism","Skills cannot directly access external APIs without MCP server integration","Skill discovery is file-system based; no centralized registry or marketplace","CLAUDE.md is manually maintained — no automatic sync with code changes","Large CLAUDE.md files consume token budget; no built-in compression or summarization","No conflict resolution for concurrent edits to CLAUDE.md across team members","Context injection happens at prompt time, adding latency for very large files","Sessions are stored locally; no built-in synchronization across machines","Session size grows with conversation history; no automatic pruning or summarization","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.4828712146702062,"quality":0.6,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.1,"match_graph":0.28,"freshness":0.12}},"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:22.065Z","last_scraped_at":"2026-05-03T14:23:44.761Z","last_commit":"2026-03-19T01:40:59Z"},"community":{"stars":1721,"forks":193,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=mcp-wesammustafa-claude-code-everything-you-need-to-know","compare_url":"https://unfragile.ai/compare?artifact=mcp-wesammustafa-claude-code-everything-you-need-to-know"}},"signature":"cclMb/OR1sBclUCD6txxVdAcOHLAPTwvYqmS/tQlIAe9rIc1dESuvhIQWFEuV2Adjfiss4ejfOk4d5i4wEAkCw==","signedAt":"2026-06-20T09:38:01.387Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/mcp-wesammustafa-claude-code-everything-you-need-to-know","artifact":"https://unfragile.ai/mcp-wesammustafa-claude-code-everything-you-need-to-know","verify":"https://unfragile.ai/api/v1/verify?slug=mcp-wesammustafa-claude-code-everything-you-need-to-know","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"}}