how to prevent openspec skill trigger by default even the repo doesn't have the openspec configuration

[veerumallavarapu]

I see an issues if the user installs the openspec and then prompt AI to explore and propose on any repo, which is by default triggering the openspe propose commands even though the repo doesn't initialized the openspec. how to prevent openspec skill trigger by default even the repo doesn't have the openspec configuration. Is there any solution or guardrails already exist ? I currently using the openspec v1.7.0. My proposal is , if user trying the prompts like explore or propose then skill can first check on that repo config.yaml exist or not, and if not exist it can go through the normal general propose not the openspec.

[veerumallavarapu]

global skills need a way to scope themselves to initialized repos only