agentleFS
theYahiatheYahia/parasut-mcp/.claude/skills/issue-efatura/SKILL.md

issue-efatura

Skill1 starsChanged 5 months agoMITView on GitHub

Officialize a Parasut sales invoice as an e-Fatura or e-Arşiv

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are 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.

  • 3

    Very specific

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

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

    If the invoice does not exist yet, create it first with create_sales_invoice.

    line 6
  2. Very specific:

    Call issue_e_document with the sales_invoice_id and recipient_vkn.

    line 7
  3. Very specific:

    If the job status is not yet done/error, call get_trackable_job with the returned job id to poll again.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

You need an existing sales invoice and the recipient's tax number (VKN/TCKN).

  1. If the invoice does not exist yet, create it first with create_sales_invoice.
  2. Call issue_e_document with the sales_invoice_id and recipient_vkn. It automatically:
    • looks up the recipient's e-Fatura inbox by VKN,
    • issues an e-Fatura if they are registered, or an e-Arşiv if not,
    • waits for the async job and returns its status.
  3. If the job status is not yet done/error, call get_trackable_job with the returned job id to poll again.
  4. Report back: which document type was issued (e-Fatura vs e-Arşiv) and the final job status.

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.