Detect and check structured data, machine-readable descriptions of page content, and generate suitable Schema.org JSON-LD snippets. Get a report of missing fields, syntax errors, and markup issues, plus code prepared for implementation.
Plan related articles by grouping keywords that share Google search results. Define a central guide, supporting articles, and internal links, then review the structure in an interactive map while checking for overlapping keyword targets.
Organize SEO work into five stages, from keyword research and backlinks to page improvements, conversions, and local search. Apply a library of 41 prompts, selecting relevant guidance for the page and its current challenges.
Audit multilingual and regional websites for hreflang errors, the annotations that connect language versions. Generate corrected tags or sitemaps, and check for missing translations, inconsistent local formats, and content that needs cultural adaptation.
Use live DataForSEO data to research search results, keyword demand, backlinks, and competitors. Compare findings in tables, inspect page issues, and track how brands or websites are mentioned and cited in AI responses.
Audit the technical factors that affect how search engines discover and index a website. Check crawl access, URLs, security, mobile pages, loading performance, and JavaScript rendering, then report measured results with prioritized fixes.
Compare a page with search results to identify mismatches in page type, content, and user needs. Receive alignment scores, assessments for different audience profiles, prioritized improvements, and optional outlines of current and proposed page layouts.
Assess web content for usefulness, readability, depth, and evidence of experience and expertise. Get quality scores and improvement suggestions, review how clearly content supports AI citations, and clean up formulaic phrasing and invisible characters in drafts.
Create an SEO strategy for a new or existing website, tailored to its industry, competitors, goals, and resources. Produce a site structure, content calendar, technical priorities, and phased implementation roadmap with measurable targets.
Turn supplied text, files, or approved URLs into linked Obsidian notes with source records and evidence tracking. Review proposed changes before applying them, preserve original materials, and record contradictions or gaps in support.
Create a source-linked rollup of a selected batch of Obsidian wiki log entries. Preview the complete draft while preserving original entries and child pages, then optionally apply the rollup and its index updates together.
Create and update Obsidian canvas boards by arranging notes, media, text, and links into visual maps. Inspect existing boards for missing files and broken connections, and preview validated changes before applying them through recoverable transactions.
Answer questions using a selected Obsidian vault, a collection of linked notes, without changing its files. Choose a search depth and receive answers with page references, clearly identified uncertainty, conflicting evidence, and any missing information.
Review consequential or ambiguous decisions through ten stages of structured reflection. Separate observations from assumptions, examine alternatives and risks, and produce a recommendation supported by evidence, with verification needs and conditions for revisiting the decision.
Research a defined topic within agreed limits and produce a cited report that distinguishes evidence, inference, contradictions, and gaps. Public web access requires consent, and saving findings or merging them into existing Obsidian notes receives separate review.
Prepare readable Markdown from HTTPS article pages using an optional external Defuddle cleaner. The workflow checks URLs, requires network consent and executable review, previews extracted content, and can retain the cleaned source separately from wiki ingestion.
Build and validate Obsidian Bases files that display notes as tables, cards, or lists. Define filters, calculated values, displayed properties, and summaries to create reading lists, task trackers, and other database-like views of existing notes.
Set up a new Obsidian vault, a folder for linked notes, or adopt an existing one. Select the working vault and route requests to the appropriate skills for importing sources, answering questions, saving results, or maintenance.
Check or configure how an Obsidian vault organizes knowledge, then suggest destinations for new notes using Generic, LYT, PARA, or Zettelkasten. Preview configuration changes before applying them; existing notes stay in place.
Find relevant passages in an Obsidian vault using a local word-based search index. Optionally reorder results by meaning with a multilingual Nomic model, returning note paths and snippets while leaving the original notes unchanged.
Check whether the official Obsidian command-line interface is ready, then use it to read and search a selected vault. Access supported backlinks and tags, with direct file reading as a fallback when the interface is unavailable.
Preserve a selected answer, decision, insight, or conversation summary as an Obsidian note. Check for duplicates, retain uncertainty, and preview the note together with related index and log updates before applying the reviewed changes.
Draft and check Obsidian notes using its Markdown extensions. Get help with note properties, internal links, embedded content, callouts, equations, and Mermaid diagrams, with checks for formatting consistency and locally verifiable link targets.
Run repeatable, read-only checks on an Obsidian wiki to find broken or ambiguous links, isolated pages, missing metadata, empty sections, outdated index entries, and source-record issues. Review findings with paths, line numbers, and counts.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)