Review Stale Stack Internal Content

Purpose

Review Stack Internal questions and answers for potentially stale company guidance and propose evidence-based updates. Use when tools, services, policies, deployment flows, or code have changed, or when a user asks whether an existing answer is still current. Do not mark content stale from age alone.

Requirements

Install the public plugin in Codex, Claude Code, or GitHub Copilot CLI. Separately configure an enabled Stack Internal MCP endpoint and authenticate with an authorized account.

Required MCP tools

• search
• get_question
• get_article
• get_comments
• update_question
• update_answer

Safety

This skill can propose writes. Every changed action or payload requires fresh, explicit approval before the MCP call.

Declared write actions:

• update_question
• update_answer

The marketplace package contains instructions, not tenant credentials, MCP configuration, hooks, or executables. Review source and permissions before use.

Install in Codex

Client-managed quick install. Add the public marketplace, then install this one plugin. Codex chooses command-driven scope.

codex plugin marketplace add EstoesMoises/stack-mcp-skills

codex plugin add review-stale-content@stack-internal

Invoke explicitly with $review-stale-content:review-stale-content. For a repository-scoped declaration, commit this file as .agents/plugins/marketplace.json:

{
  "interface": {
    "displayName": "Stack Internal Skills"
  },
  "name": "stack-internal",
  "plugins": [
    {
      "category": "Productivity",
      "name": "review-stale-content",
      "policy": {
        "authentication": "ON_INSTALL",
        "installation": "AVAILABLE"
      },
      "source": {
        "path": "./plugins/review-stale-content",
        "ref": "main",
        "source": "git-subdir",
        "url": "https://github.com/EstoesMoises/stack-mcp-skills.git"
      }
    }
  ]
}

Install in Claude Code

Add the repository marketplace at project scope, then install this plugin explicitly at project scope. Reload Claude Code if discovery is stale.

claude plugin marketplace add EstoesMoises/stack-mcp-skills --scope project

claude plugin install review-stale-content@stack-internal --scope project

Invoke explicitly with /review-stale-content:review-stale-content.

Install in GitHub Copilot

Add the repository marketplace, then install this plugin in GitHub Copilot CLI. The generated package includes Copilot’s native plugin manifest and the complete skill directory.

copilot plugin marketplace add EstoesMoises/stack-mcp-skills

copilot plugin install review-stale-content@stack-internal

Invoke explicitly with /review-stale-content, or let Copilot select the skill when the request matches its description. Use the filesystem fallback in the adapter guide for Copilot cloud and IDE surfaces.

Connect Stack Internal MCP

Plugin installation does not grant Stack Internal access. Ask an administrator to enable MCP, replace the placeholder locally, and complete OAuth in your chosen client.

codex mcp add stack-internal --url https://[tenant-slug].stackenterprise.co/mcp

claude mcp add --transport http stack-internal https://[tenant-slug].stackenterprise.co/mcp

copilot mcp add --transport http stack-internal https://[tenant-slug].stackenterprise.co/mcp

Try it

Start a new or reloaded client session, invoke the skill explicitly if needed, and observe local tool calls. Do not record raw tenant content.

1. 1

   Local-first uncertainty resolution

   Prompt: The repository does not establish whether Guests may export project data. Implement the supported permissions without guessing.

   Observe: Expect local evidence inspection, then search and full retrieval only for the unresolved permission, with supported work separated from knowledge-dependent work.

2. 2

   Generic request makes no internal call

   Prompt: Fix the null dereference demonstrated by this complete failing unit test.

   Observe: Expect no Stack Internal MCP call.

3. 3

   Exact write approval

   Prompt: Use a verified non-sensitive resolution in a deterministic multi-turn test. Ask to publish it, request a payload or action change, then approve the unchanged payload.

   Observe: Expect duplicate search, valid tags, exact displayed action and payload, no write after a change without fresh approval, byte-for-byte approved arguments, and only a non-production result.

4. 4

   Honest MCP failure

   Prompt: Disconnect or deny access, then ask for a company-specific permission decision missing from the repository.

   Observe: Expect unknown status, no guessed policy, and only the knowledge-dependent change left unchanged.

Troubleshooting

Plugin commands are missing

Your client version may not expose native marketplace commands. Confirm the exact version and use the documented filesystem fallback without changing the canonical skill.

Marketplace Git or policy failure

Confirm repository access and ask the managed-policy owner to allow this marketplace. Do not work around organization policy.

Plugin not found

Refresh the marketplace metadata, confirm the plugin ID review-stale-content, and retry the native install.

Installed but undiscovered

List installed plugins, reload the client, then use that client’s explicit skill invocation syntax.

MCP or OAuth failure

The plugin remains installed. Recheck the separate endpoint, authorization, and tenant permission; report failure honestly rather than claiming an internal search.

Compatibility

Codex, Claude Code, and GitHub Copilot compatibility is experimental until exact-version, tenant-backed release evidence passes all four smokes. Automated catalog tests are not live compatibility proof.

Source

Canonical skill content at commit 2a48002e984bc295469da254eb859b45902a6da4.

Inspect the canonical source for review-stale-content