Markdown Converter
Agent skill for markdown-converter
**ALWAYS follow this sequence**:
Sign in to like and favorite skills
ALWAYS follow this sequence:
mcp_oraios_serena_activate_project "KenmeiToAnilist" - Activate project firstget_symbols_overview, find_symbol, search_for_pattern, list_dir)think_about_collected_information after gathering contextthink_about_task_adherence before committing changesthink_about_whether_you_are_done to verify completionKEY: Use Serena tools for discovery, not reading files unless necessary. Always read any relevant memories for context if needed. Memories are for context only, NOT documentation summaries. Never summarize changes or create summary documents unless explicitly asked to, this applies to things outside of memories as well.
Always
when I need code generation, setup or configuration steps, or
library/API documentation. This means you should automatically use the Context7 MCP
tools to resolve library id and get library docs without me having to explicitly ask.use context7
Default modes:
["planning", "editing"]
Always assume the default modes are active to ensure modes are correctly set and you don't forget to change them.
Always use the
switch_modes tool to adapt modes based on task complexity. NOTE: Reserve interactive only for large or risky changes that require clarification; avoid interactive for routine small edits to reduce unnecessary prompts.
| Task Type | Modes | When to Use |
|---|---|---|
| Trivial fixes | | Skip planning overhead, make & verify immediately |
| Small edits | | Quick changes — avoid interactive prompts; no detailed planning needed |
| Medium features | | Brief 3–6 item plan, explore, edit incrementally; only use interactive when clarification is required |
| Large/risky changes | + extra verification | Thorough planning & verification at every checkpoint |
Thinking Tools — Use at Relevant Checkpoints:
think_about_collected_information → After exploring code, verify context is sufficient before editingthink_about_task_adherence → Before making changes, confirm the approach is still correctthink_about_whether_you_are_done → After completing work, verify all requirements are metUse these thinking tools whenever applicable, not just for the largest changes.
get_symbols_overview: High-level view of top-level symbols in a filefind_symbol: Locate specific symbol by name path with optional depthsearch_for_pattern: Regex search when you don't know exact symbol nameslist_dir: Understand project structurefind_file: Search files by glob patternBest Practice: Always explore with these tools BEFORE reading files. Saves tokens and time.
runSubagent tool to launch a single-run, stateless autonomous agent for bounded, repeatable tasks (e.g., repo-scoped refactors, triage, or research).subagent-usage (use read_memory to access the reference).Use memories for context only:
Do NOT write memories for: Documentation summaries, code overviews, or API reference (use Serena tools instead).
Critical Success Factors: