agentleFS
Sign inStart free
ieeecsopenieeecsopen/mcp-cs/skills/algo-plagiarism-detector/SKILL.md

algo-plagiarism-detector

Skill3 starsChanged 3 months agoNo licenceView on GitHub

Activate this skill whenever a user asks to check whether two code submissions are plagiarized, copied, cloned, or "too similar" — trigger phrasings include "check if these two submissions are plagiarized", "did team B copy team A's code", "compare these two solutions for academic dishonesty", "is this a clone of that repo", "run a similarity check on this contest entry", or "audit these assignments for copying". Applies to competitive-programming contest judging (hackathon entries, CTF writeups, algorithm-round submissions) and academic integrity reviews of student coursework. Wraps the MCS `algo_check_plagiarism` tool, which performs token-level, identifier-normalized, Winnowing-fingerprint comparison (Jaccard similarity over k-gram hashes) between exactly two source files and returns a calibrated verdict.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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