agentleFS
Sign inStart free
olgasafonovaolgasafonova/mediawiki-mcp-server/skills/wiki-operations/SKILL.md

wiki-operations

Skill23 starsChanged 7 days agoMITView on GitHub

Search, read, and analyze MediaWiki content. Use for finding information, checking page quality, tracking changes, and exploring wiki structure.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use mediawiki_search_in_page instead of fetching entire pages just to find text.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Wiki Operations

Trigger

Searching, reading, or analyzing content on a MediaWiki wiki.

Workflow

  1. Search for content — Use mediawiki_search for full-text search across the wiki. Use mediawiki_search_in_page when you know the specific page.
  2. Read pages — Use mediawiki_get_page with the exact page title. If the title might be wrong, use mediawiki_resolve_title first (handles case sensitivity and typos).
  3. Explore structure — Use mediawiki_get_sections to see page structure, mediawiki_list_categories for topic browsing, mediawiki_get_category_members for pages in a category.
  4. Check quality — Use mediawiki_check_links for broken external URLs, mediawiki_find_broken_internal_links for broken wiki links, mediawiki_find_orphaned_pages for unlinked pages, mediawiki_check_terminology for naming consistency.
  5. Track changes — Use mediawiki_get_revisions for page history, mediawiki_compare_revisions for diffs, mediawiki_get_recent_changes for recent activity (supports aggregation by user, page, or type), mediawiki_get_user_contributions for a specific editor's work.
  6. Find related content — Use mediawiki_get_related for pages connected by categories and links, mediawiki_find_similar_pages for content-based similarity, mediawiki_compare_topic to see how a term is described across pages.
  7. Convert content — Use mediawiki_convert_markdown to transform Markdown to wikitext. Supports themes: tieto, neutral, dark.

Guardrails

  • Page titles are case-sensitive. Use mediawiki_resolve_title when unsure.
  • Use mediawiki_search_in_page instead of fetching entire pages just to find text.
  • For aggregated change reports, use the aggregate_by parameter on mediawiki_get_recent_changes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free