Claude Skills by tools-only

**URL**: https://www.linkedin.com/posts/rakeshgohel01_i-still-think-claude-code-is-an-underrated-activity-7426689113375940608-dJCz/ **Date de publication**: 9 février 2026 **Auteur du post**: Rakesh Gohel (141K followers LinkedIn) **Auteur de l'infographie**: Aakash Gupta (PM content creator, newsletter news.aakashg.com) **Format**: Post LinkedIn + Infographie 1-page "Master Claude Code v1.0" **Engagement**: 630 likes, 34 commentaires **Date d'évaluation**: 10 février 2026 ---

3-layer defense, sandbox decision, verification paradox, CI/CD pipeline

Ask Claude for multiple approaches with trade-offs before coding to prevent anchoring bias

**Purpose**: Enable real-time session statistics with official Claude Code metrics **When to use**: Setting up Navigator for the first time, enabling ROI measurement **Last Updated**: 2025-10-20 ---

Using planning-with-files inside [BoxLite](https://boxlite.ai) micro-VM sandboxes via [ClaudeBox](https://github.com/boxlite-ai/claudebox). ---

Infrastructure as Code best practices for Azure Terraform templates. AVM-first, CAF naming, security baseline.

Quick reference to monorepo management skills for TypeScript/JavaScript projects. ---

MANDATORY Azure Policy compliance rules for Terraform code generation. Azure Policy always wins.

   <details open> <summary><strong>📑 Deployment Summary</strong></summary> - [✅ Preflight Validation](#-preflight-validation) - [📋 Deployment Details](#-deployment-details) - [🏗️ Deployed Resources](#️-deployed-resources) - [📤 O...

Complete guide for creating minimal AWS Lambda functions in pure Java without frameworks.

Complete deployment patterns for PHP Lambda functions using Serverless Framework and AWS SAM.

This reference covers deployment strategies, CI/CD pipelines, and optimization techniques for NestJS Lambda applications using AWS SAM and Serverless Framework.

Deployment patterns for Python Lambda functions using Serverless Framework, AWS SAM, and CI/CD pipelines.

Complete guide for deploying Java Lambda functions with Serverless Framework, AWS SAM, and CI/CD pipelines.

Complete guide for building AWS Lambda functions with the AWS Chalice framework.

```bash npx create-nx-workspace@latest ```

from fastmcp import FastMCP mcp = FastMCP("awesome-server", version="0.1.0") @mcp.tool def echo(text: str) -> str: """Return the provided text.""" return text def main() -> None: """Entry point for `python -m awesome_server.server_fastmcp`.""" mcp.run() # stdio by default if __name__ == "__main__": # pragma: no cover main() ``` **Enhanced Server with Native HTTP Support** - For better flexibility, add argument parsing to support both stdio and HTTP modes natively: ```python from fastmcp imp...

**Current Version: 1.0.0-RC-1** — The gateway ships with the controls described below. Everything listed here is present in the codebase today; future roadmap items live in `docs/docs/architecture/roadmap.md`.

Complete guide for exporting Aldea slide decks to PDF and static HTML. ---

This document provides an **architecture-focused reference** for designing systems using the **Model Context Protocol (MCP)**. It covers **MCP server patterns**, **agent/host orchestration patterns**, and **anti-patterns**, with a strong emphasis on scalability, governance, and security. ---

This guide shows how to operate the **ContextForge Stack** with a *Git-Ops* workflow powered by [Argo CD](https://argo-cd.readthedocs.io). Once wired up, every commit to the repository becomes an automatic deployment (or rollback) to your Kubernetes cluster. > 🌳 Git source of truth: > `https://github.com/IBM/mcp-context-forge` > > * **App manifests:** `deployment/k8s/` (Kustomize-ready) > * **Helm chart (optional):** `charts/mcp-stack` ---

The `cforge gateway` command is a powerful deployment tool for ContextForge and its external plugins. It provides a unified, declarative way to build, configure, and deploy the complete MCP stack from a single YAML configuration file.

Running **ContextForge** with **Compose** spins up a full stack (Gateway, Postgres, Redis, optional MCP servers) behind a single YAML file. The Makefile detects Podman or Docker automatically, and you can override it with `COMPOSE_CMD=`. Health-checks (`service_healthy`) gate the Gateway until the database is ready, preventing race conditions. If dependencies become temporarily unavailable, the Gateway uses **exponential backoff with jitter** for connection retries—see [Startup Resilience](.....

This guide covers the complete deployment workflow for the **ContextForge** on Fly.io, including common troubleshooting steps. ---

This privacy policy describes how **Skill Agent** (the “Plugin”) processes data when used in Dify.

ContextForge can be deployed to [Google Cloud Run](https://cloud.google.com/run), a fully managed, autoscaling platform for containerized applications. This guide provides step-by-step instructions to provision PostgreSQL and Redis backends, deploy the container, configure environment variables, authenticate using JWT, and monitor logs-all optimized for cost-efficiency. ---

import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import Image from '@theme/IdealImage';

This guide walks you through installing, upgrading, and removing the full **ContextForge Stack** using Helm. The stack includes: * 🧠 ContextForge (the gateway) * 🗄 PostgreSQL database * ⚡ Redis cache * 🧑💻 PgAdmin UI (optional) * 🧰 Redis Commander UI (optional) Everything is deployable via Helm on any Kubernetes cluster (Minikube, kind, EKS, AKS, GKE, OpenShift, etc.). > 📦 Helm chart location: > [https://github.com/IBM/mcp-context-forge/tree/main/charts/mcp-stack](https://github.com/IBM/...

This guide covers two supported deployment paths for the **ContextForge**: 1. **Makefile automation** - a single-command workflow that wraps `ibmcloud` CLI. 2. **Manual IBM Cloud CLI** - the raw commands the Makefile executes, for fine-grained control. ---

Provides comprehensive security review for TypeScript/Node.js applications (Next.js, NestJS, Express, etc.). Use when auditing security vulnerabilities or before deploying to production.

This guide walks you through running ContextForge on your local machine using a virtual environment or directly via Python. ---

1. **Install Minikube and kubectl** (Docker or Podman driver required). 2. Start a local cluster with Ingress and DNS addons. 3. Load the `ghcr.io/ibm/mcp-context-forge:1.0.0-RC-1` image into Minikube. 4. Apply your Kubernetes manifests. 5. Access the Gateway at [http://gateway.local](http://gateway.local) or `127.0.0.1:80` via NGINX Ingress. Minikube provides a self-contained environment, enabling you to replicate production features like persistent volumes and TLS on your local machine. ---

This guide explains how to configure ContextForge to work with authentication proxies like OAuth2 Proxy, Authelia, Cloudflare Access, or enterprise API gateways.

> Follow this checklist to set up your development environment, verify all features, and ensure consistent onboarding across ContextForge project. ---

ContextForge's Admin UI supports flexible section visibility for embedding in third-party portals, restricting views for specific audiences, and reducing dashboard clutter. This guide covers environment-level configuration, per-request hiding, and embedded mode. !!! info "UI Visibility vs. RBAC" Section visibility is a **UI convenience**, not a security boundary. Hidden sections are still accessible via API. Use [RBAC](rbac.md) to control data access.

Configure ContextForge to work with authentication proxies for enterprise deployments.

> Comprehensive guide to scaling ContextForge from development to production, covering vertical scaling, horizontal scaling, connection pooling, performance tuning, and Kubernetes deployment strategies.

This guide provides essential security configurations and best practices for deploying ContextForge in production environments.

When integrating with internal or development MCP servers that use self-signed TLS certificates, you must provide the Certificate Authority (CA) root certificate to the gateway. This allows the gateway to verify the identity of the remote server and establish a secure connection. This guide explains how to upload and manage custom CA certificate bundles for registered MCP servers.

This tutorial walks you through setting up generic OpenID Connect (OIDC) Single Sign-On (SSO) authentication for ContextForge, enabling integration with any OIDC-compliant identity provider including Keycloak, Auth0, Authentik, and others.

This tutorial walks you through setting up Google Single Sign-On (SSO) authentication for ContextForge, allowing users to log in with their Google accounts.

This tutorial walks you through setting up Keycloak Single Sign-On (SSO) authentication for ContextForge, enabling enterprise identity management with the popular open-source identity and access management solution.

!!! note "Multi‑Tenancy (introduced in v0.7.0)" Multi‑tenancy (email authentication, teams, RBAC, resource visibility) was introduced in v0.7.0. If you're upgrading from 0.6.0, review the [Migration Guide](https://github.com/IBM/mcp-context-forge/blob/main/MIGRATION-0.7.0.md) and [Changelog](https://github.com/IBM/mcp-context-forge/blob/main/CHANGELOG.md). For SSO deployments, configure group‑to‑team mappings to auto‑assign users on first login. See [Team Management](teams.md) and the provide...

> This page collects practical levers for squeezing the most performance, reliability, and observability out of **ContextForge**-no matter where you run the container (Code Engine, Kubernetes, Docker Compose, Nomad, etc.). > > **TL;DR** > > 1. Tune the **runtime environment** via `.env` and configure mcpgateway to use PostgreSQL and Redis. > 2. Adjust **Gunicorn** workers & time-outs in `gunicorn.conf.py`. > 3. Right-size **CPU/RAM** for the container or spin up more instances (with shared Re...

This guide provides step-by-step instructions for upgrading ContextForge and handling associated database migrations to ensure a smooth transition with minimal downtime. ---

Well-known URIs are standardized endpoints that web services expose for automated discovery and security contact purposes, as defined by RFC 8615. ContextForge provides configurable support for standard well-known URIs with security-first defaults.

ContextForge provides robust configuration validation tools to help operators catch misconfigurations early and ensure reliable deployments.

This guide documents the CPU spin loop issue affecting ContextForge and the multi-layered mitigation strategy implemented to address it.

ContextForge includes a built-in Admin UI for managing all entities in real time via a web browser. ---

!!! warning "Preview" This guide is in preview and will continue to evolve. Content is accurate but may receive refinements as the Helm chart and GitOps flows mature. !!! abstract "What you'll achieve" * Build or pull the OCI image(s) for ContextForge * Push them to **IBM Container Registry (ICR)** * Provision an **IKS** cluster with VPC-native networking * Install & bootstrap **Argo CD** for GitOps management * Deploy the MCP Stack Helm chart via Argo CD * Configure ContextForge with servers...