Developing Smart Contracts
LFDT-Lineth/lineth-monorepo
Solidity smart contract development guidelines for Lineth blockchain.
Mark one or more superchain-ops tasks as EXECUTED by updating each task README's Status line to link the on-chain execution transaction, then open a PR.
Install Mark Task Executed
$ npx skills add ethereum-optimism/superchain-ops --skill mark-task-executed -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ethereum-optimism/superchain-ops mark-task-executed --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ethereum-optimism/superchain-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mark-task-executed .claude/skills/mark-task-executed && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mark-task-executed" agent skill from https://github.com/ethereum-optimism/superchain-ops/tree/main/.claude/skills/mark-task-executed into .claude/skills/mark-task-executed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mark-task-executed", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ethereum-optimism/superchain-ops/tree/main/.claude/skills/mark-task-executedType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ethereum-optimism/superchain-ops --skill mark-task-executed -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ethereum-optimism/superchain-ops mark-task-executed --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ethereum-optimism/superchain-ops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/mark-task-executed .agents/skills/mark-task-executed && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mark-task-executed" agent skill from https://github.com/ethereum-optimism/superchain-ops/tree/main/.claude/skills/mark-task-executed into .agents/skills/mark-task-executed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mark-task-executed", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ethereum-optimism/superchain-ops --skill mark-task-executed -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ethereum-optimism/superchain-ops mark-task-executed --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ethereum-optimism/superchain-ops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/mark-task-executed .cursor/skills/mark-task-executed && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mark-task-executed" agent skill from https://github.com/ethereum-optimism/superchain-ops/tree/main/.claude/skills/mark-task-executed into .cursor/skills/mark-task-executed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mark-task-executed", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ethereum-optimism/superchain-ops.git --path .claude/skills/mark-task-executed--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ethereum-optimism/superchain-ops --skill mark-task-executed -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ethereum-optimism/superchain-ops mark-task-executed --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ethereum-optimism/superchain-ops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/mark-task-executed .gemini/skills/mark-task-executed && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mark-task-executed" agent skill from https://github.com/ethereum-optimism/superchain-ops/tree/main/.claude/skills/mark-task-executed into .gemini/skills/mark-task-executed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mark-task-executed", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ethereum-optimism/superchain-ops mark-task-executedInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ethereum-optimism/superchain-ops --skill mark-task-executed -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ethereum-optimism/superchain-ops.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/mark-task-executed .github/skills/mark-task-executed && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mark-task-executed" agent skill from https://github.com/ethereum-optimism/superchain-ops/tree/main/.claude/skills/mark-task-executed into .github/skills/mark-task-executed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mark-task-executed", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ethereum-optimism/superchain-ops --skill mark-task-executed -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ethereum-optimism/superchain-ops mark-task-executed --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ethereum-optimism/superchain-ops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/mark-task-executed .opencode/skills/mark-task-executed && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mark-task-executed" agent skill from https://github.com/ethereum-optimism/superchain-ops/tree/main/.claude/skills/mark-task-executed into .opencode/skills/mark-task-executed/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mark-task-executed", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mark-task-executed- GitHub stars
- 100
- Token cost
- ~679 tokens
- SKILL.md length
- 321 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Mark one or more superchain-ops tasks as EXECUTED by updating each task README's Status line to link the on-chain execution transaction, then open a PR.
- Works in 5 steps: Map each task to its execution tx hash.… → Find each task directory:… → Edit the status line per the convention… → …
- A task (or batch of tasks) has been executed on-chain and someone shares the execution tx hash(es)
- SKILL.md covers The convention, Steps and Notes
- Reaches etherscan.io and sepolia.etherscan.io
What it does
Mark Task Executed is an agent skill from ethereum-optimism/superchain-ops. Mark one or more superchain-ops tasks as EXECUTED by updating each task README's Status line to link the on-chain execution transaction, then open a PR. Use when a task (or batch of tasks) has been executed on-chain and someone shares the execution tx hash(es).
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Smart contracts, Pull requests and Technical documentation. It works with Ethereum. The repository describes itself as: superchain-ops allows builders to create and execute tasks on EVM chains. The licence is MIT.
When your agent uses it
- A task (or batch of tasks) has been executed on-chain and someone shares the execution tx hash(es)
- Tasks that involve Smart contracts
- Tasks that involve Pull requests
Example prompts
- “/mark-task-executed”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Map each task to its execution tx hash. The requester usually provides
- Find each task directory: src/tasks//<###>-/README.md.
- Edit the status line per the convention above for each task.
- Verify each edited line: grep -rn '^Status:' src/tasks/**/README.md.
- Open a PR (docs-only, no CI simulation needed). Use a title like
What it can do on your machine
Read from SKILL.md and the folder at commit ec439d9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
etherscan.iosepolia.etherscan.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Mark Task Executed loads about 679 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 321 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ethereum-optimism/superchain-ops at commit ec439d9, republished under its MIT licence (© ethereum-optimism). 321 words, ~679 tokens.
Download SKILL.mdSave it as
.claude/skills/mark-task-executed/SKILL.md (or your agent's skills folder).- name
- mark-task-executed
- description
- Mark one or more superchain-ops tasks as EXECUTED by updating each task README's Status line to link the on-chain execution transaction, then open a PR. Use when a task (or batch of tasks) has been executed on-chain and someone shares the execution tx hash(es).
Mark a superchain-ops task as EXECUTED
When a governance task has been executed on-chain, its README.md status line
must be updated from the pre-execution state to EXECUTED with a link to the
execution transaction. This is a docs-only change — no Solidity, config, or
validation files change.
The convention
Every task README.md begins with a title and a status line:
# 056-fus-rotation-1
Status: [READY TO SIGN]()Marking it executed means replacing only the status line's label and link:
Status: [EXECUTED](https://etherscan.io/tx/0x<hash>)- The status label may currently be
[READY TO SIGN](),[READY TO EXECUTE](),[SIGNED](), etc. — replace whatever is there with[EXECUTED](<tx-url>). - Network → explorer base URL:
src/tasks/eth/...(Ethereum mainnet) →https://etherscan.io/tx/<hash>src/tasks/sep/...(Sepolia) →https://sepolia.etherscan.io/tx/<hash>- For other networks, use that network's canonical block explorer tx URL.
- Do not touch any other line in the README, and do not edit
config.tomlorVALIDATION.md.
Steps
- Map each task to its execution tx hash. The requester usually provides them (e.g. "056 → 0xabc…"). Match by the leading task number. If a mapping is ambiguous, ask rather than guess — a wrong tx link on a governance task is a correctness bug.
- Find each task directory:
src/tasks/<network>/<###>-<name>/README.md. (ls src/tasks/eth | grep '^056'.) - Edit the status line per the convention above for each task.
- Verify each edited line:
grep -rn '^Status:' src/tasks/**/README.md. Confirm the label isEXECUTED, the hash matches what was provided, and the explorer base URL matches the network. - Open a PR (docs-only, no CI simulation needed). Use a title like
docs: mark <network> tasks <###>-<###> as EXECUTED. List each task and its tx link in the body so reviewers can spot-check hashes against the explorer.
Notes
- This is a fast, cheap, low-risk change: string edits to markdown status lines. Batch multiple tasks into one PR.
- Recent examples for the exact diff shape: PRs #1494, #1457, and the "executed" PRs in the merge history.
- Reviewers should confirm each tx hash on the linked explorer actually corresponds to the task's execution (correct Safe, correct calldata) before merging.
© ethereum-optimism, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/mark-task-executed of ethereum-optimism/superchain-ops.
Open the folder on GitHubat commit ec439d9
Compare with similar skills
Mark Task Executed next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mark Task Executed this skillethereum-optimism/superchain-ops | 100 | — | ~679 | Automated safety check: Pass | MIT | |
| Developing Smart ContractsLFDT-Lineth/lineth-monorepo | 126 | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 | |
| Gh Update PR Descriptionlidofinance/staking-modules | 119 | — | ~568 | Automated safety check: Pass | GPL-3.0 | |
| Dev Serverlablup/backend.ai-webui | 133 | — | ~6.9k | Automated safety check: Notes | LGPL-3.0 | |
| Post Draft Reviewagent-substrate/substrate | 4.5k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Review Kedro PRkedro-org/kedro | 11k | — | ~2.8k | Automated safety check: Pass | Custom licence |
Similar skills
Gh Update PR Description
lidofinance/staking-modules
Update the current-branch GitHub PR title, description, and labels with gh CLI using this repository's PR template.
Dev Server
lablup/backend.ai-webui
Start the project's development server (pnpm dev for backend.ai-webui; discovered from README/package.json elsewhere), deriving the header color, app name, default backend endpoint and login…
Post Draft Review
agent-substrate/substrate
Posts pull request review findings as GitHub draft (pending) inline comments for a human to edit and submit, instead of publishing them straight to the PR author.
Review Kedro PR
kedro-org/kedro
Review a Kedro PR for checklist compliance, architecture, correctness, and clarity.
Opik Documentation Patterns
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
More from ethereum-optimism/superchain-ops
Fix Check Superchain Registry
ethereum-optimism/superchain-ops
Diagnose and fix a failing checksuperchainregistry CircleCI job on superchain-ops, typically caused by the pinned lib/superchain-registry submodule drifting from upstream main.
Related
Works with
Categories
Questions about Mark Task Executed
What does Mark Task Executed do?
Mark one or more superchain-ops tasks as EXECUTED by updating each task README's Status line to link the on-chain execution transaction, then open a PR. Mark Task Executed is an agent skill from ethereum-optimism/superchain-ops. Mark one or more superchain-ops tasks as EXECUTED by updating each task README's Status line to link the on-chain execution transaction, then open a PR.
When should I use Mark Task Executed?
Mark Task Executed fits situations like: A task (or batch of tasks) has been executed on-chain and someone shares the execution tx hash(es); tasks that involve Smart contracts; tasks that involve Pull requests.
How do I install Mark Task Executed in Claude Code?
Run `npx skills add ethereum-optimism/superchain-ops --skill mark-task-executed -a claude-code`. Or copy the skill folder (.claude/skills/mark-task-executed in ethereum-optimism/superchain-ops) into .claude/skills/mark-task-executed in your project. Claude Code loads it when a task matches its description.
How do I install Mark Task Executed in Codex?
Run `npx skills add ethereum-optimism/superchain-ops --skill mark-task-executed -a codex`. Or copy the skill folder (.claude/skills/mark-task-executed in ethereum-optimism/superchain-ops) into .agents/skills/mark-task-executed in your project. Codex loads it when a task matches its description.
Can I use Mark Task Executed in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ethereum-optimism/superchain-ops --skill mark-task-executed -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mark-task-executed, .gemini/skills/mark-task-executed, .github/skills/mark-task-executed and .opencode/skills/mark-task-executed in your project.
What does Mark Task Executed need to run?
SKILL.md names no scripts, command-line tools or credentials: Mark Task Executed is instructions for the agent only.
Does Mark Task Executed access the network?
SKILL.md names 2 domains. In commands or code: etherscan.io and sepolia.etherscan.io; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Mark Task Executed safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Mark Task Executed use?
Mark Task Executed is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Mark Task Executed use?
About 679 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Mark Task Executed?
Skills that share tags, products or a category with Mark Task Executed: Developing Smart Contracts (LFDT-Lineth/lineth-monorepo, 126 stars), Gh Update PR Description (lidofinance/staking-modules, 119 stars), Dev Server (lablup/backend.ai-webui, 133 stars) and Post Draft Review (agent-substrate/substrate, 4.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mark Task Executed?
ethereum-optimism (a GitHub organization) maintains it in ethereum-optimism/superchain-ops, which has 100 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 5, 2026.
Source: ethereum-optimism/superchain-ops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.