360 Secure SkillHub
360 安全技能中心

Test my skill

该 Skill 自述为用于测试、没有任何实际意义的条目。正文为无结构的占位字符,夹带一段关于其他 Go 项目缺陷与重构设想的笔记(文件可见性、OAuth、数据模型与删除接口等),未定义任何实际能力、输入输出、命令、配置或使用方式。

wayne-huangyj
wayne-huangyj
热度 56.65
最近更新 2026-05-11 17:32:53
分类:开发依赖:纯提示词

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add test-my-skill
Metadata
name
test-my-skill
description
没有任何实际意义的skill,用于测试

~ . File visibility bug: buildSkillArchive (in bootstrap.go) only creates a tar.gz with SKILL.md! So Phabricator-bootstrapped skills only have SKILL.md visible. The StreamSkillContent function only fetches SKILL.md too. This is the core bug explaining why "only SKILL.md is visible".

  1. Microsoft OAuth: Currently only static token-based auth stub. Need proper MS OAuth.

  2. Owner model: OwnerTokenHash is a single hash, not multi-owner. Need SkillOwner junction table.

  3. Missing delete endpoint: No way to remove skills via API.

So my plan is to tackle the database redesign first—adding a User table and SkillOwner junction table to support multiple owners. Then I'll implement Microsoft OAuth with proper Azure AD integration, fix the file visibility issue by making StreamSkillContent fetch the entire skill directory from Phabricator instead of just SKILL.md, and add the missing delete endpoint.

Looking at the actual implementation, the core problem is in bootstrap.go where StreamSkillContent only retrieves SKILL.md. I need to refactor it to use the directory-fetching logic from gitfetch.go so it pulls all files in the skill directory. Before diving into the code changes, I should clarify the scope with the user and understand their priorities—this is a substantial refactor that touches the database layer, authentication, file handling, and API structure. I'm seeing the core issues now: the Phabricator bootstrap only archives SKILL.md, so I need to either make StreamSkillContent fetch the full directory recursively or trigger a re-fetch when the editor opens. For the OAuth piece, I'll use Azure AD with MSAL, storing the user's OID and email. The owner model should shift from a token hash to a junction table or JSON array of user OIDs. For the delete endpoint, I need to clean up the Repository, Manifests, Tags, and any orphaned Blobs. Let me document all these changes in a plan. o

sad as d sad sad as dsa d as d sad sa d