How do I install the Speq Code Tools skill?

Run npx skillmds@latest add marconae/speq-code-tools in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Speq Code Tools safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Speq Code Tools?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Speq Code Tools free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Speq Code Tools?

marconae (@marconae) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Speq Code Tools by marconae — Agent Skill

Name: Speq Code Tools
Author: marconae

Speq Code Tools

Semantic code navigation and editing via Serena MCP — symbol-level tools required over grep/find/manual edits. Triggered by planner-agent, implementer-agent, implementer-expert-agent, code-reviewer, and recorder-agent.

marconae 63b165b 2.5 KB Updated Sep 17, 2026

File contents

Code Tools

Semantic code navigation and editing via Serena MCP. Tools are called mcp__plugin_speq_serena__<name> (e.g. mcp__plugin_speq_serena__find_symbol); this skill refers to them by short name below.

Before First Use Each Session

Call initial_instructions first, before any other Serena tool.
These tools are deferred in this harness — a bare tool name has no loaded schema yet. Call ToolSearch with select:mcp__plugin_speq_serena__<name> (comma-separated for several) to load the ones you need before calling them.

Tool Preference

You MUST use these instead of the generic alternative — do not fall back to Read/Grep/Edit/ls/find for anything this table covers.

Task	Use	Not
List directory	`list_dir`	`ls`, `find`
Find files	`find_file`	`find`, `rg --files`
File symbols	`get_symbols_overview`	`rg "class\|function"`
Symbol definition	`find_symbol`	`rg "function foo"`
Symbol declaration	`find_declaration`	`rg` guesswork
Symbol references	`find_referencing_symbols`	`rg "foo("`
Interface/method implementations	`find_implementations`	`rg "impl .* for"`
LSP diagnostics for a file	`get_diagnostics_for_file`	manual build/check
Update function	`replace_symbol_body`	read/edit/write
Insert after	`insert_after_symbol`	read/edit/write
Insert before	`insert_before_symbol`	read/edit/write
Rename symbol	`rename_symbol`	`rg` + manual edits
Delete symbol	`safe_delete_symbol`	manual delete + grep for refs
In-file text/regex replace	`replace_content`	read/edit/write
Multi-file pattern replace	`replace_in_files`	multiple manual edits

Memory tools (write_memory, read_memory, list_memories, delete_memory, edit_memory, rename_memory) exist and are available, but this project's specs (specs/, specs/_plans/.../notes/) are the source of truth — they are not part of this workflow.

Workflow

Session start → initial_instructions
Explore → find_symbol, get_symbols_overview, find_declaration
Understand → find_referencing_symbols, find_implementations
Edit → replace_symbol_body, insert_*_symbol, replace_content, replace_in_files
Verify → find_referencing_symbols, get_diagnostics_for_file

---name: speq-code-toolsdescription: Semantic code navigation and editing via Serena MCP — symbol-level tools required over grep/find/manual edits. Triggered by planner-agent, implementer-agent, implementer-expert-agent, code-reviewer, and recorder-agent.---# Code ToolsSemantic code navigation and editing via Serena MCP. Tools are called `mcp__plugin_speq_serena__<name>` (e.g. `mcp__plugin_speq_serena__find_symbol`); this skill refers to them by short name below.## Before First Use Each Session1. Call `initial_instructions` first, before any other Serena tool.2. These tools are deferred in this harness — a bare tool name has no loaded schema yet. Call `ToolSearch` with `select:mcp__plugin_speq_serena__<name>` (comma-separated for several) to load the ones you need before calling them.## Tool PreferenceYou MUST use these instead of the generic alternative — do not fall back to `Read`/`Grep`/`Edit`/`ls`/`find` for anything this table covers.| Task | Use | Not ||------|-----|-----|| List directory | `list_dir` | `ls`, `find` || Find files | `find_file` | `find`, `rg --files` || File symbols | `get_symbols_overview` | `rg "class\|function"` || Symbol definition | `find_symbol` | `rg "function foo"` || Symbol declaration | `find_declaration` | `rg` guesswork || Symbol references | `find_referencing_symbols` | `rg "foo("` || Interface/method implementations | `find_implementations` | `rg "impl .* for"` || LSP diagnostics for a file | `get_diagnostics_for_file` | manual build/check || Update function | `replace_symbol_body` | read/edit/write || Insert after | `insert_after_symbol` | read/edit/write || Insert before | `insert_before_symbol` | read/edit/write || Rename symbol | `rename_symbol` | `rg` + manual edits || Delete symbol | `safe_delete_symbol` | manual delete + grep for refs || In-file text/regex replace | `replace_content` | read/edit/write || Multi-file pattern replace | `replace_in_files` | multiple manual edits |Memory tools (`write_memory`, `read_memory`, `list_memories`, `delete_memory`, `edit_memory`, `rename_memory`) exist and are available, but this project's specs (`specs/`, `specs/_plans/.../notes/`) are the source of truth — they are not part of this workflow.## Workflow```Session start → initial_instructionsExplore → find_symbol, get_symbols_overview, find_declarationUnderstand → find_referencing_symbols, find_implementationsEdit → replace_symbol_body, insert_*_symbol, replace_content, replace_in_filesVerify → find_referencing_symbols, get_diagnostics_for_file```

Frequently asked questions