Created a new Package for espanso - OASIS-IS Prompt Framework

[Ryfter]

This is a mega-prompt framework form for prompting in ChatGPT, Claude and other chatbots. It has two modes.

1. Using it in a URL bar or any text field it creates a prompt that will run in chatGPT. This is the base version that allows users to get the full prompt in the form of a URL. This only works for ChatGPT.
2. This is meant to be used in any prompt box. It does not include the URL, but just the text for the prompt.

[smeech]

That's an impressive piece of work, which passes all the automated checks.

I am interested to note that although the indentation of the triggers as a whole, and also the first replace: block, doesn't follow our convention, and sets off a lot of linter warnings here, it still works. It's good to question these things!

No script:, shell:, cmd: or malicious code.

specification: is empty in both triggers - just checking this is correct, and I take it :poasis doesn't need a model: section?

There's a lot of duplicated code between the two expansions, which could be shared using Global Variables or Anchors and Aliases? I've put a suggestion here for your interest. As I say in the comments, it's not pretty!

[Ryfter]

Thank you for your comments. I'll dig into it, and optimize it. I spent most of Sunday just getting that far. I appreciate you taking the time to give me feedback.

:Oasisform creates a prompt as a URL. You can see it in action better in the spreadsheet I created for it: http://3dmkf.com/pace-oasis You fill out the fields in E2 to E8. I converted that into an espanso form. It inserts the model as part of the URL.

The other one :poasis , the p stands for prompt. It is meant to go into the prompt. So, in ChatGPT, you choose the model from the dropdown in the top left of the chat screen.

[smeech]

Thank you. That's neat.

formo1 throws linter errors here, but works nevertheless.

To make it more tidy, I was playing around with trying to separate the Interpretation values list into an echo: global_var, but hadn't managed to make it work.

Just one critical problem - the path version (currently 0.1.0) has to match the version: value in _manifest.yml (now 0.1.1), I'm afraid, before the CI will accept it.

Once this is fixed, and you're happy with the package, I'll merge it.

A few more typos, by line number:
5. Evaluate
6. available
8. will
17. & 30. additional

[smeech]

Thank you! That now passes all the CI checks.

There are still a few typos - you might wish to correct the one at the top of README.md at least, as it's the one likely to be seen (the ones in the package.yml comments, less so)!

Let me know when you're happy, and I'll hit the Merge button.