Repository navigation
docs: apply the operational data positioning to the README, manifests, skills and evals - #20
Open
HasanAlpCaferoglu wants to merge 1 commit into
Open
HasanAlpCaferoglu wants to merge 1 commit into
HasanAlpCaferoglu wants to merge 1 commit into
Conversation
…, skills and evals
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this change?
Applies the operational data positioning from DataSQRL/sqrl#2608 (
POSITIONING.md, the blog post and the comparison page) to the plugin. The plugin version is now0.4.1.ghcr.io/datasqrl/adv-agent). The pro edition is the pro agent (ghcr.io/datasqrl/pro-agent), which is not open source. The launcher image names do not change.shortDescription,longDescriptionanddefaultPrompttexts. The marketplace description now describes the catalog.startskill description: adds the triggers Kafka, CDC, data product and operational data pipeline. All old triggers stay.startskill, "Using DataSQRL": opens with the boilerplate, defines operational data, and names SQRL. It lists the six fit signals and a rule to decide the fit by where the work runs and who consumes the result. It adds the warehouse fit (CDC into Iceberg, with views for each query engine) and the non-fit for scheduled models in a warehouse (dbt or SQLMesh). It lists the tools that DataSQRL works with and does not replace.startcases,dbt-models-not-a-fitandwarehouse-landing-is-a-fit.Area
scripts/datasqrl-agent.sh)scripts/datasqrl-cloud.sh)scripts/datasqrl-agent.shchanges only in one comment and one error message, for the rename.How did you test it?
.github/check-plugin.shpasses with version0.4.1.shellcheckwas not installed locally, so only CI runs that lint step.pytest tests: 174 passed. This run was before the README reflow, the marketplace description change and the version change. The tests read none of those files.tests/claude-plugin-evals/skill-specific-tests, 3 runs each: all 13 cases scored 1.00, with the two new cases. The fourstartcases scored 1.00 again after the last change to thestartskill.patch-small-change-runs-patch: 0.92 against the 0.8 threshold. One of 3 runs did not give the run name in its reply.Checklist
feat:,fix:ordocs:.github/check-plugin.shpasses