Skip to content

Easier Genie Code Install Options #387

@Zachary-Higgins-Altera

Description

@Zachary-Higgins-Altera

Hi - I found the Genie Code install for Genie Code to be unnecessarily complicated and not compatible with Genie Code. It doesn't seem like you can run it from a notebook in the workspace. install_skills.sh is a pre-req for install_skills_to_genie_code.sh, but install_skills.sh doesn't run unless we're in a project directory which is defined in the following code block:

# Check if we're in a git repo or project directory
if [ ! -d ".git" ] && [ ! -f "pyproject.toml" ] && [ ! -f "package.json" ] && [ ! -f "databricks.yml" ]; then
    echo -e "${YELLOW}Warning: This doesn't look like a project root directory.${NC}"
    echo -e "Current directory: $(pwd)"
    read -p "Continue anyway? (y/N): " confirm
    if [ "$confirm" != "y" ] && [ "$confirm" != "Y" ]; then
        echo "Aborted."
        exit 1
    fi
fi

This conflicts with the official documentation that states skills in Genie Code live in the workspace level user home directory (not project): https://learn.microsoft.com/en-us/azure/databricks/genie-code/skills

Skills live in the /Users/{username}/.assistant/skills/ directory. Each skill must have its own folder and a SKILL.md file within that folder.

... so there probably won't be a pyproject.toml, package.json, or databricks.yml in the user's home folder. I don't know, maybe the assumption is that users would try to run this from a project, and then the installer would do its job and eventually we would migrate to the workspace level skills dir? But what if the workspace is fresh? There are too many assumptions with this pattern in my opinion.

Please consider providing something like this to give users an easy way to install these to their workspace (just run a notebook).
https://gist.github.com/Zachary-Higgins-Altera/943a0e162bd6ffe6ab56e32d07652a46

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions