<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.speedsolving.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Kryptonite</id>
	<title>Speedsolving.com Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.speedsolving.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Kryptonite"/>
	<link rel="alternate" type="text/html" href="https://www.speedsolving.com/wiki/index.php/Special:Contributions/Kryptonite"/>
	<updated>2026-11-02T19:14:15Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://www.speedsolving.com/wiki/index.php?title=Skeleton&amp;diff=14315</id>
		<title>Skeleton</title>
		<link rel="alternate" type="text/html" href="https://www.speedsolving.com/wiki/index.php?title=Skeleton&amp;diff=14315"/>
		<updated>2011-03-18T13:40:26Z</updated>

		<summary type="html">&lt;p&gt;Kryptonite: Created page with &amp;quot;A skeleton is a nearly finished solution in a Fewest Moves solve.  The intent behind a skeleton is to do the majority of the solve, then insert the final moves somewhere within t...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A skeleton is a nearly finished solution in a Fewest Moves solve.  The intent behind a skeleton is to do the majority of the solve, then insert the final moves somewhere within the skeleton that give fewer moves than performing a different algorithm at the end.  A common technique is to create a skeleton leaving 3-5 corners, then review their position throughout the solution to find the optimal place to insert (an) 8-move commutator(s) that ideally cancel moves within the skeleton.&lt;br /&gt;
&lt;br /&gt;
While 3-5 corners is the most common skeleton configuration, a skeleton could essentially take any form--such as leaving a three edge cycle.  However, corner cycles are generally considered the most effective, largely because Fewest Move solves are judged in HTM, and edge cycles depend on slice moves.&lt;/div&gt;</summary>
		<author><name>Kryptonite</name></author>
	</entry>
</feed>