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

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

Commencer

read-temp-file

Étoiles42

Forks20

Mis à jour15 mai 2026 à 22:28

Reads the content of a file located in the temporary directory (temp/) which is otherwise ignored by git.

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

blockscout

blockscout/mcp-server

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

2 fichiers

SKILL.md

readonly

name	read-temp-file
description	Reads the content of a file located in the temporary directory (temp/) which is otherwise ignored by git.

Read Temp File Skill

This skill allows you to safely read files from the project's temporary directory temp/, bypassing standard git-ignore restrictions.

Instructions

When you need to read a file from the temp/ directory (e.g., to verify the content of a generated issue description):

Do NOT use the read_file tool. It will fail for ignored files.
Instead, use the run_shell_command tool to execute the helper script.
Command format: python3 .gemini/skills/read-temp-file/scripts/read_temp_file.py <file_path>

Example

To read temp/gh_issues/issue_description.md:

python3 .gemini/skills/read-temp-file/scripts/read_temp_file.py temp/gh_issues/issue_description.md

Constraints

The file must be inside the temp/ directory.
The file must not be binary.
The file must not exceed 2000 lines.

Plus depuis ce dépôt

même dépôt

address-plan-findings

blockscout/mcp-server

Validate review findings about an implementation plan against the codebase and repo rules, fix the valid ones in the plan, and write a feedback file noting what changed and what was rejected (and why). For plan-review findings, not code-review findings.

2026-07-1642

implementation-plan-review

blockscout/mcp-server

Expert review of an implementation plan against a GitHub issue/enhancement description (provided as a local file or a GitHub issue URL) and the current repository codebase. Use when asked to critique a plan for correctness, completeness, codebase alignment, risks, and test/rollout readiness (do not implement).

2026-07-1642

review-plan-findings-feedback

blockscout/mcp-server

Manually review a feedback file produced after implementation-plan review findings were addressed. Use when the user asks to read a findings-feedback file and verify that the plan changes correctly close, correctly reject, or fail to close the original implementation-plan-review findings, while checking for newly introduced or newly exposed plan problems. Writes only new findings to the plan-id findings directory and replies with the output file path or a concise no-new-findings status.

2026-07-1642

sepolia-foundry-tx

blockscout/mcp-server

Use this skill whenever the agent needs to deploy a smart contract to Sepolia testnet via Foundry (`forge create` or `forge script --broadcast`), routed through the Blockscout PRO API's JSON-RPC gateway instead of a third-party RPC provider. Trigger on requests like "deploy this contract to Sepolia", "deploy via Foundry", "broadcast this Foundry deployment script", or any `forge create`/`forge script` invocation that needs a signer and an RPC endpoint for Sepolia (chain id 11155111) in this project. Also consult it to find which local Foundry keystore to sign with — this project stores test signing keys as encrypted keystores under `.ai/wallet/`, never as a plain private key in `.env`. Do not use this for reads (balances, transaction history, contract info) — use the connected Blockscout MCP tools for those directly; this skill is specifically about broadcasting a deployment.

2026-07-1642

address-code-review-comments

blockscout/mcp-server

Enter the worktree of a GitHub PR, validate the code-review comments raised on it against what the code actually does and the repo rules, fix the valid ones directly in the PR's source/tests, and report in chat — a brief note per closed comment and a detailed plain-language explanation of every comment left unclosed and why. For code-review comments on a PR. Invoke manually.

2026-06-1942

consult-spec

blockscout/mcp-server

TRIGGER CONDITIONS - invoke this skill when ANY of these apply: User-triggered (explicit request): - User mentions "specification", "SPEC", "SPEC.md", "spec requirements" - User asks to "verify with spec", "confirm with specification", "check requirements" - User requests "authoritative requirements" or "source of truth" Agent self-triggered (during reasoning): - Before implementing any feature or making code changes - When verifying technical requirements or constraints - When making architectural or design decisions - When you need unbiased guidance not influenced by current implementation - When encountering conflicting information and need ground truth PURPOSE: Consults SPEC.md through an isolated subagent that ONLY reads the specification, never implementation code. This ensures guidance is based on authoritative requirements, not potentially incorrect existing code.

2026-06-1942

name	read-temp-file
description	Reads the content of a file located in the temporary directory (temp/) which is otherwise ignored by git.

Read Temp File Skill

This skill allows you to safely read files from the project's temporary directory temp/, bypassing standard git-ignore restrictions.

Instructions

When you need to read a file from the temp/ directory (e.g., to verify the content of a generated issue description):

Do NOT use the read_file tool. It will fail for ignored files.
Instead, use the run_shell_command tool to execute the helper script.
Command format: python3 .gemini/skills/read-temp-file/scripts/read_temp_file.py <file_path>

Example

To read temp/gh_issues/issue_description.md:

python3 .gemini/skills/read-temp-file/scripts/read_temp_file.py temp/gh_issues/issue_description.md

Constraints

The file must be inside the temp/ directory.
The file must not be binary.
The file must not exceed 2000 lines.