[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BXYDAA9F64EMN1ZGFWXTMX":3,"skill-same:01M6BXYDAA9F64EMN1ZGFWXTMX":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":12,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6BXYDAA9F64EMN1ZGFWXTMX","api-settings",null,"Call nodetool.settings or nodetool.secrets from a code action: read or change a NodeTool setting, find out which credentials are configured, ask the user to enter a missing API key, or read a secret in a script. Load before the first call into these namespaces.","nodetool-ai\u002Fnodetool","nodetool-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F164873569?v=4","01M6BXPFDW36K9K1MR8ZH63HG2","nodetool.ai","01M6BXPFJ893XM219GQN60B0WK",635,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fapi-settings\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"api","api settings","settings","read","load","namespaces","action","which","script","missing","call","user","change","ask","find","nodetool","secrets","credentials","first","code","2026-11-10 10:12:30",false,"---\nname: api-settings\ndescription: \"Call nodetool.settings or nodetool.secrets from a code action: read or change a NodeTool setting, find out which credentials are configured, ask the user to enter a missing API key, or read a secret in a script. Load before the first call into these namespaces.\"\n---\n\n# nodetool.settings and nodetool.secrets\n\n`nodetool.settings` is the configuration of this install. `nodetool.secrets`\nreads credentials inside a run. A secret value never passes through the agent:\nthe user types it in a dialog.\n\n## nodetool.settings\n\n| Call | Does | Answers |\n| :--- | :--- | :--- |\n| `list({group})` | Lists every setting, or one group (`\"Folders\"`, for example), with its description, allowed values and current value. Secrets are not in this list. | `{settings, groups}` |\n| `get(key)` | Reads one setting, from the user's saved settings and then the environment. Refuses a secret. | The setting with its `value` and `source` (`user`, `env` or `unset`) |\n| `set(key, value)` | Changes one setting for this user. Only a declared setting can be set, and a setting with allowed values takes only those. `value` is a string. | — |\n| `secrets()` | Lists the known credentials and whether each one is configured. | Names and a configured flag. Never values. |\n| `requestSecret(key, {reason, help_url})` | Opens a dialog in the user's client where they type the value. | Only whether they saved one |\n\n`key` is the environment-variable name: `\"AUTOSAVE_INTERVAL_MINUTES\"`,\n`\"STRIPE_API_KEY\"`.\n\n### Asking for a credential\n\n1. Call `secrets()` to see what is missing, and use the name the service is\n   registered under.\n2. Call `requestSecret(key, {reason, help_url})`. Write `reason` for the user,\n   in one sentence. `help_url` is where they get the key.\n3. Continue when the answer says it was saved.\n\nA run with no interactive client refuses the request. Then tell the user\nwhich credential is missing and where to add it (Settings > Secrets). Do not\nask again in a loop, and never ask the user to paste a key into the chat.\n\n## nodetool.secrets\n\nFor code that needs a credential value, such as a Code node or a script:\n\n| Call | Does |\n| :--- | :--- |\n| `get(name)` | The value. It throws and names the secret when it is not set. |\n| `tryGet(name)` | The value, or `undefined` for a credential that is optional |\n| `list()` | The names this node declared in its secret scope, or `null` when it declared none |\n\nA read works only for a name inside the secret scope of the run. A chat\naction has no secret store, so `nodetool.secrets.get` throws there. Use the\ntools that hold the credential on the host instead of reading it.\n","# nodetool.settings and nodetool.secrets\n\n`nodetool.settings` is the configuration of this install. `nodetool.secrets`\nreads credentials inside a run. A secret value never passes through the agent:\nthe user types it in a dialog.\n\n## nodetool.settings\n\n| Call | Does | Answers |\n| :--- | :--- | :--- |\n| `list({group})` | Lists every setting, or one group (`\"Folders\"`, for example), with its description, allowed values and current value. Secrets are not in this list. | `{settings, groups}` |\n| `get(key)` | Reads one setting, from the user's saved settings and then the environment. Refuses a secret. | The setting with its `value` and `source` (`user`, `env` or `unset`) |\n| `set(key, value)` | Changes one setting for this user. Only a declared setting can be set, and a setting with allowed values takes only those. `value` is a string. | — |\n| `secrets()` | Lists the known credentials and whether each one is configured. | Names and a configured flag. Never values. |\n| `requestSecret(key, {reason, help_url})` | Opens a dialog in the user's client where they type the value. | Only whether they saved one |\n\n`key` is the environment-variable name: `\"AUTOSAVE_INTERVAL_MINUTES\"`,\n`\"STRIPE_API_KEY\"`.\n\n### Asking for a credential\n\n1. Call `secrets()` to see what is missing, and use the name the service is\n   registered under.\n2. Call `requestSecret(key, {reason, help_url})`. Write `reason` for the user,\n   in one sentence. `help_url` is where they get the key.\n3. Continue when the answer says it was saved.\n\nA run with no interactive client refuses the request. Then tell the user\nwhich credential is missing and where to add it (Settings > Secrets). Do not\nask again in a loop, and never ask the user to paste a key into the chat.\n\n## nodetool.secrets\n\nFor code that needs a credential value, such as a Code node or a script:\n\n| Call | Does |\n| :--- | :--- |\n| `get(name)` | The value. It throws and names the secret when it is not set. |\n| `tryGet(name)` | The value, or `undefined` for a credential that is optional |\n| `list()` | The names this node declared in its secret scope, or `null` when it declared none |\n\nA read works only for a name inside the secret scope of the run. A chat\naction has no secret store, so `nodetool.secrets.get` throws there. Use the\ntools that hold the credential on the host instead of reading it.\n",{"name":5,"description":7},"main","c7226baa82daca42a19a5855c116544f97aa8bac","packages\u002Fsystem-skills\u002Fapi-settings",91,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool","https:\u002F\u002Fnodetool.ai\u002F","https:\u002F\u002Fgithub.com\u002Fnodetool-ai","No-code AI development","2026-11-15 03:27:49",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add nodetool-ai\u002Fnodetool --skill api-settings",{"tool":69,"command":70},"bunx","bunx skills add nodetool-ai\u002Fnodetool --skill api-settings",{"tool":72,"command":73},"pnpm","pnpm dlx skills add nodetool-ai\u002Fnodetool --skill api-settings","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fapi-settings\u002FSKILL.md",true,[],[78,87,118,148,163,179],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"01M742MX3Y2ZYK884ZXTRFKB9P","humanizer","Rewrite AI-sounding text so it reads like the writer without changing what it says.\nUse when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line\nclosers, staged openers, forced triads, dashes everywhere, inflated claims, sales\nlanguage, stock AI words, bold labels, or filler.","MIT","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhumanizer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":88,"name":44,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":96,"publishedAt":49},"01M6BY4D93R0Q9400ZHJ04DXP1","Use the NodeTool MCP server to build, validate, run, and debug visual AI workflows, and to work with assets, collections, and jobs. Use when the user mentions NodeTool or asks for a workflow graph, a node, or a media generation run on their NodeTool server.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fplugins\u002Fchatgpt\u002Fnodetool\u002Fskills\u002Fnodetool\u002FSKILL.md",[92,95],{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[44,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117],"MCP","Media","workflows","when","generation","media generation","with","visual","use","collections","for","node","work","debug","graph","validate","assets","run","server","mcp server","workflow",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":127,"publishedAt":49},"01M6BY4AEB05ZPBRVD078ATR2H","wan-2-6-prompting","Prompt Alibaba's Wan 2.6 video — text-to-video with a global style line plus timing-bracketed shots, and image-to-video that describes only what changes over time. Covers the shot-mode switch per provider, the prompt budget, negative prompts, motion intensity wording, audio input and prompt expansion. Use whenever the model id names a Wan 2.6 video route (alibaba\u002Fwan-2.6\u002Ftext-to-video, alibaba\u002Fwan-2.6\u002Fimage-to-video, wan-video\u002Fwan-2.6-t2v, wan-video\u002Fwan-2.6-i2v, wan-video\u002Fwan2.6-i2v-flash) on generate_video, animate_image or a TextToVideo node. Not for Wan 2.5 or 2.7, or the Wan 2.6 image routes.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fwan-2-6-prompting\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[128,129,130,131,132,133,134,108,135,136,137,138,139,140,141,142,143,144,145,146,147],"prompting","wan 2 6 prompting","line","expansion","input","image-to-video","text-to-video","route","only","mode","time","flash","Budget","generate","text","image","animate","model","Audio","Video",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":156,"publishedAt":49},"01M6BY47T4748ZG5ZMTAR97ZWZ","video-workflow","Build a reusable NodeTool video workflow for batches or repeated inputs. For a single finished piece, use a storyboard skill.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fvideo-workflow\u002FSKILL.md",[154,155],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},[117,157,147,158,159,160,161,105,162,44,107],"video workflow","reusable","storyboard","build","batches","single",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":170,"publishedAt":49},"01M6BY4587N2SYN315SXGEMZC3","video-clone","Analyze a reference video and recreate its shot structure with a new product or cast in NodeTool.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fvideo-clone\u002FSKILL.md",[169],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[171,172,147,103,173,174,44,175,176,177,178],"clone","video clone","cast","new","analyze","product","structure","reference",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":186,"publishedAt":49},"01M6BY4257C2KQYYMD9EK6DK8E","video-audio-continuity","Keep sound continuous across a multi-scene piece cut from generated video — why one clip per scene hard-cuts the audio at every boundary, when to write all the scenes into a single generation instead, the sound-design vocabulary that survives a provider's copyright filter, and how to check the length, the aspect ratio and the mix of what came back. Use when a piece has more than one scene and the video model writes its own audio (Seedance 2, Veo 3, MiniMax H3, Kling 2.6 and later), or when a cut's sound drops out at the shot changes.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fvideo-audio-continuity\u002FSKILL.md",[185],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[187,147,146,188,189,190,191,192,193,194,195,196,197,100,198,199,145,200,201,202,203],"video audio continuity","continuity","write","why","back","veo 3","at","cut","later","across","filter","generated","how to","mix","design","boundary","how"]